CN113886696A

CN113886696A - Data pushing method, label processing method, device, system and computer equipment

Info

Publication number: CN113886696A
Application number: CN202111166079.1A
Authority: CN
Inventors: 黎子群; 张默; 洪淼; 齐霁; 张跃; 黄少文
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2021-09-30
Filing date: 2021-09-30
Publication date: 2022-01-04

Abstract

The application relates to a data pushing method, a label processing method, a device, a system and a storage medium. The embodiment of the invention can be applied to vehicle-mounted scenes. The method comprises the following steps: responding to configuration operation of data pushing, and displaying pushing configuration information; the push configuration information comprises data to be pushed and target user tags, wherein the user tags are tags configured for user identifications by the first server based on user behavior data in the target application; responding to the confirmation operation aiming at the pushing configuration information, generating a data pushing task based on the pushing configuration information, and sending the data pushing task to a transfer terminal, so that the transfer terminal responds to the confirmation operation aiming at the data pushing task and pushes the data to be pushed to a target user terminal corresponding to the target user label. By adopting the method, the data pushing efficiency can be improved.

Description

Data pushing method, label processing method, device, system and computer equipment

Technical Field

The present application relates to the field of computer technologies, and in particular, to a data pushing method, a tag processing method, an apparatus, a system, a computer device, and a storage medium.

Background

With the increasing development of computer technology, data push has become an important content of current network technology application, and people can obtain various push data through a terminal, such as news messages, weather reports, product introduction messages, and the like.

In the conventional technology, a data sender edits data to be pushed on a sending terminal, selects a data receiver, and then sends the data to be pushed to a receiving terminal corresponding to the data receiver through the sending terminal. The whole process is complicated to operate, so that the data pushing efficiency is low.

Disclosure of Invention

In view of the above, it is necessary to provide a data pushing method, a tag processing method, an apparatus, a system, a computer device, and a storage medium, which can improve data pushing efficiency, in order to solve the above technical problems.

A data pushing method is applied to a management terminal, and comprises the following steps:

responding to configuration operation of data pushing, and displaying pushing configuration information; the push configuration information comprises data to be pushed and target user tags, wherein the user tags are tags configured for user identifications by the first server based on user behavior data in the target application;

responding to the confirmation operation aiming at the pushing configuration information, generating a data pushing task based on the pushing configuration information, and sending the data pushing task to a transfer terminal, so that the transfer terminal responds to the confirmation operation aiming at the data pushing task and pushes the data to be pushed to a target user terminal corresponding to the target user label.

In one embodiment, in response to a configuration operation of data push, displaying push configuration information includes:

displaying a push task configuration interface; responding to a push data selection operation triggered on the push task configuration interface, and determining the data to be pushed; and determining the target user tag in response to a user tag selection operation triggered on the push task configuration interface.

In one embodiment, the pushing configuration information further includes at least one of a target pushing manner and a target relay user identifier, and the displaying the pushing configuration information in response to the configuration operation of data pushing includes:

responding to a transit user identifier selection operation triggered on the push task configuration interface, and determining the target transit user identifier; the transfer terminal is a user terminal corresponding to the target transfer user identifier; and determining the target pushing mode in response to a pushing mode selection operation triggered on the pushing task configuration interface.

In an embodiment, when the target pushing manner is a session pushing manner, the target pushing manner is used to push the data to be pushed to a target session interface as a target session message, where the target session interface is a session interface of the relay terminal and the target user terminal in an associated application corresponding to the target application.

In an embodiment, when the target pushing manner is a dynamic information pushing manner, the target pushing manner is used to send the data to be pushed to the target user terminal as target dynamic information, so that the target user terminal displays the target dynamic information on a dynamic information display interface in the target application.

A data pushing device, the device comprising:

the push information configuration module is used for responding to configuration operation of data push and displaying push configuration information; the push configuration information comprises data to be pushed and target user tags, wherein the user tags are tags configured for user identifications by the first server based on user behavior data in the target application;

and the pushing task generating module is used for responding to the confirmation operation aiming at the pushing configuration information, generating a data pushing task based on the pushing configuration information, and sending the data pushing task to the transfer terminal, so that the transfer terminal responds to the confirmation operation aiming at the data pushing task and pushes the data to be pushed to the target user terminal corresponding to the target user label.

A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:

A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:

A data pushing method is applied to a transit terminal, and comprises the following steps:

displaying a data pushing task sent by a management terminal; the data pushing task is generated by the management terminal in response to a confirmation operation aiming at pushing configuration information based on the pushing configuration information, the pushing configuration information is obtained by the management terminal in response to a configuration operation of data pushing, and the pushing configuration information comprises data to be pushed and a target user label; the user label is a label configured for each user identifier by the first server based on user behavior data in the target application;

and responding to the confirmation operation aiming at the data pushing task, and pushing the data to be pushed to a target user terminal corresponding to the target user label.

In one embodiment, the method further comprises:

displaying behavior track data corresponding to the current user identification in a user information display interface corresponding to the current user identification; the behavior trace data is obtained by performing behavior arrangement on the user behavior data corresponding to the current user identifier.

A data pushing device, the device comprising:

the push task display module is used for displaying the data push tasks sent by the management terminal; the data pushing task is generated by the management terminal in response to a confirmation operation aiming at pushing configuration information based on the pushing configuration information, the pushing configuration information is obtained by the management terminal in response to a configuration operation of data pushing, and the pushing configuration information comprises data to be pushed and a target user label; the user label is a label configured for each user identifier by the first server based on user behavior data in the target application;

and the pushing task execution module is used for responding to the confirmation operation aiming at the data pushing task and pushing the data to be pushed to the target user terminal corresponding to the target user label.

A tag processing method is applied to a first server, and comprises the following steps:

acquiring user behavior data corresponding to each user identifier in a target application;

determining user tags corresponding to the user identifications based on the user behavior data to form a candidate tag set;

sending the candidate tag set to a management terminal so that the management terminal can display the candidate tag set on a push task configuration interface, and determining a target user tag from the candidate tag set; the target user tag is used for carrying out data pushing, the pushing process of the data pushing is that the management terminal sends a data pushing task to the transfer terminal, so that the transfer terminal responds to the confirmation operation aiming at the data pushing task and pushes data to be pushed to the target user terminal corresponding to the target user tag, the data pushing task is generated based on pushing configuration information, and the pushing configuration information comprises the data to be pushed and the target user tag.

A label processing apparatus, the apparatus comprising:

the user data acquisition module is used for acquiring user behavior data corresponding to each user identifier in the target application;

the user label determining module is used for determining user labels corresponding to the user identifications based on the user behavior data to form a candidate label set;

the user tag sending module is used for sending the candidate tag set to a management terminal so that the management terminal can display the candidate tag set on a pushing task configuration interface and determine a target user tag from the candidate tag set; the target user tag is used for carrying out data pushing, the pushing process of the data pushing is that the management terminal sends a data pushing task to the transfer terminal, so that the transfer terminal responds to the confirmation operation aiming at the data pushing task and pushes data to be pushed to the target user terminal corresponding to the target user tag, the data pushing task is generated based on pushing configuration information, and the pushing configuration information comprises the data to be pushed and the target user tag.

A data push system comprises a management terminal, a transfer terminal, a first server and a target user terminal;

the first server is used for configuring corresponding user tags for each user identifier based on user behavior data in the target application to form a candidate tag set and sending the candidate tag set to the management terminal;

the management terminal is used for displaying the candidate tag set on a pushing task configuration interface, determining a target user tag from the candidate tag set, generating pushing configuration information based on data to be pushed and the target user tag, generating a data pushing task based on the pushing configuration information, and sending the data pushing task to the transfer terminal;

and the transfer terminal is used for responding to the confirmation operation aiming at the data pushing task and pushing the data to be pushed to the target user terminal corresponding to the target user label.

According to the data pushing method, the label processing method, the device, the system, the computer equipment and the storage medium, the first server configures corresponding user labels for the user identifications based on the user behavior data in the target application, each user label forms a candidate label set, the candidate label set is sent to the management terminal, and the candidate label set is displayed on a pushing task configuration interface of the management terminal. The management terminal responds to configuration operation triggered on the push task configuration interface and displays push configuration information, and the push configuration information comprises data to be pushed and a target user label. And the management terminal responds to the confirmation operation aiming at the push configuration information, generates a data push task based on the push configuration information and sends the data push task to the transfer terminal. And the transfer terminal responds to the confirmation operation aiming at the data pushing task and pushes the data to be pushed to the target user terminal corresponding to the target user label. Therefore, the management terminal establishes the data pushing task in a unified mode, the transfer terminal can send the data to be pushed to the target user terminal in a one-key mode only by simple confirmation operation after receiving the data pushing task, the transfer terminal does not need to manually select the data to be pushed and a data receiving party to push the data, and the data pushing efficiency is improved. In addition, the first server can automatically configure the user tag for the user identifier based on the user behavior data, so that when data pushing is carried out, a data receiving party does not need to be manually selected, the data receiving party can be quickly determined based on the target user tag, and the data pushing efficiency is further improved.

Drawings

FIG. 1 is a diagram of an application environment of a data pushing method and a tag processing method in one embodiment;

FIG. 2 is a flow chart illustrating a data pushing method according to an embodiment;

FIG. 3A is an interface diagram that illustrates an initialization interface for the management application, according to one embodiment;

FIG. 3B is a schematic diagram of an interface in the keyword tag configuration area in one embodiment;

FIG. 3C is a schematic diagram of an interface in an embodiment of an in-group behavior tag configuration area;

FIG. 3D is a schematic diagram of an interface in the interactive behavior tag configuration area, according to an embodiment;

FIG. 4 is an interface diagram of a push task configuration interface in one embodiment;

FIG. 5A is a schematic diagram of an interface for a push task configuration interface in one embodiment;

FIG. 5B is a schematic diagram of an interface for a push task configuration interface in one embodiment;

FIG. 6 is a flow chart illustrating a data pushing method according to another embodiment;

FIG. 7A is a diagram illustrating an interface displaying data push tasks, according to an embodiment;

FIG. 7B is a diagram illustrating an interface for session sharing, according to an embodiment;

FIG. 7C is a diagram illustrating an example interface for dynamic information sharing;

FIG. 8 is a schematic diagram of an embodiment of a user information presentation interface;

FIG. 9 is a flowchart illustrating a tag handling method according to an embodiment;

FIG. 10A is a schematic diagram illustrating the process of keyword tagging in one embodiment;

FIG. 10B is a schematic diagram illustrating an exemplary process for group tagging;

FIG. 10C is a schematic diagram illustrating an exemplary process for interactive tagging of material;

FIG. 11 is a block diagram of a data push system in one embodiment;

FIG. 12 is a schematic diagram of a data push system in another embodiment;

FIG. 13 is a block diagram showing the structure of a data push apparatus according to an embodiment;

FIG. 14 is a block diagram showing the construction of a data pushing apparatus according to another embodiment;

FIG. 15 is a block diagram showing the structure of a tag processing apparatus according to an embodiment;

FIG. 16 is a diagram showing an internal structure of a computer device in one embodiment;

FIG. 17 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The data pushing method and the tag processing method provided by the application can be applied to the application environment shown in fig. 1. The user terminal cluster 102 includes a plurality of user terminals corresponding to the user identifiers, and each user terminal communicates with the first server 104 through a network. In addition, the first server 104 communicates with the management terminal 106 and the relay terminal 108 via a network, and the management terminal 106 and the relay terminal 108 communicate via the network. Through data interaction with the user terminal cluster and the transit terminal, the first server 104 may obtain user behavior data of each user identifier in the target application, and configure a corresponding user tag for each user identifier based on the user behavior data. The first server 104 may send each user tag to the management terminal 106 and the relay terminal 108, and display the user tags on the management terminal 106 and the relay terminal 108. The first server 104 may generate a candidate tag set based on each user tag, send the candidate tag set to the management terminal 106, and display the candidate tag set on a push task configuration interface of the management terminal 106. The management terminal 106 may display push configuration information in response to a configuration operation triggered on the push task configuration interface, where the push configuration information includes data to be pushed and a target user tag. The management terminal 106 may generate a data push task based on the push configuration information in response to the confirmation operation for the push configuration information, and send the data push task to the relay terminal 108. After receiving the data pushing task, the transit terminal 108 may respond to a confirmation operation for the data pushing task, and push the data to be pushed to the target user terminal 110 corresponding to the target user tag. The target user terminal 110 is a user terminal corresponding to the target user tag in the user terminal cluster 102.

It is understood that the terminal may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, smart voice interaction devices, smart appliances, vehicle terminals, and portable wearable devices, and the server may be implemented by an independent server, or a server cluster formed by a plurality of servers, or a cloud server.

In an embodiment, as shown in fig. 2, a data pushing method is provided, which is described by taking the example that the method is applied to the management terminal in fig. 1, and includes the following steps:

step S202, responding to the configuration operation of data pushing, and displaying pushing configuration information; the push configuration information comprises data to be pushed and a target user label.

The management terminal refers to a terminal operated by an administrator. The administrator refers to an administrator in the user cluster and is used for managing and maintaining relevant information of the user cluster. The management terminal may run a user cluster management application, and an administrator may perform related configuration of data push in the user cluster management application.

The target of data pushing refers to pushing data to be pushed to a target user. On a related interface of the management terminal, an administrator can determine push configuration information for data push through configuration operation, and the push configuration information can be displayed on the interface.

The configuration operation is used for configuring information, and the configuration operation may specifically be a touch operation, a cursor operation, a key operation, or a voice operation. The touch operation may be a touch click operation, a touch press operation, or a touch slide operation, and the touch operation may be a single-point touch operation or a multi-point touch operation, for example, on a related interface of the management terminal, the data to be pushed is determined by the touch click operation for the candidate pushed data set. The cursor operation may be an operation of controlling a cursor to click or an operation of controlling a cursor to press, for example, on a related interface of the management terminal, the data to be pushed is determined by a cursor click operation for the candidate data pushing option. The key operation may be a virtual key operation or an entity key operation, for example, on a relevant interface of the management terminal, the data to be pushed is input through the key operation for the entity key of the management terminal.

The push configuration information specifically includes data to be pushed and a target user tag. The data to be pushed may include information content of at least one data type, and specifically may include but is not limited to at least one of text, expression, image, video, file, link address, and other data. For example, the data to be pushed may be a group invitation two-dimensional code, a product introduction short video, a to-be-developed activity introduction tweet with rich pictures and texts, and the like. The target user tag is at least one user tag determined from a plurality of candidate tags based on the configuration operation.

Specifically, a user cluster management application may be run on the management terminal, and the user cluster management application serves a user cluster communication application. The user cluster communication application is an instant communication application designed for team users, and team staff can carry out work conversation through the team communication application and also can carry out at least one of office functions such as file transmission, information statistics, daily attendance, conference reservation or mail exchange through the team communication application so as to assist the team staff to work and realize cooperative work among the team staff. For example, the user cluster communication application may be an enterprise communication application, the user cluster including individual enterprise members. The user cluster management application may be referred to simply as a management application.

The administrator can log in the management application on the management terminal, and perform configuration operation related to data push in the management application. The management terminal can respond to the configuration operation of the data push of the administrator, and the configured push configuration information is displayed to the administrator on the management terminal. For example, the administrator may determine the data to be pushed and the target user tag by selecting from a candidate pushed data set and a candidate tag set presented by the management terminal.

Wherein the candidate tag set is a tag set composed of a plurality of candidate user tags. The user tag is configured for each user identifier by the first server based on the user behavior data in the target application.

The first server is an application server corresponding to the management application, and can perform data analysis on target behavior data of the user in the target application and automatically configure a corresponding user tag for the user. The target application refers to an individual communication application, the individual communication application and the user cluster communication application are instant communication applications, and an association relationship exists between the two applications, so that the individual user and a cluster user in a user cluster can perform information exchange across the applications. In communicating information, individual users may use user accounts in individual communication applications, while clustered users may use user accounts in user-clustered communication applications. It will be appreciated that user behavior data is generated during the communication of information. The user behavior data records interaction information of the individual user and the cluster user, for example, a session message between the individual user and the cluster user, browsing behavior of the individual user on push data sent by the cluster user, and the like. In order to improve the efficiency of pushing data to an individual user by a cluster user, a first server may obtain user behavior data of the individual user in a target application, perform data analysis on the user behavior data based on a certain algorithm and a certain strategy, and determine a user tag corresponding to the individual user, so as to configure the corresponding user tag for the individual user. The first server may determine the individual users based on the user identifiers, that is, each user identifier is a user identifier corresponding to each individual user.

Step S204, responding to the confirmation operation aiming at the pushing configuration information, generating a data pushing task based on the pushing configuration information, and sending the data pushing task to the transfer terminal, so that the transfer terminal responds to the confirmation operation aiming at the data pushing task and pushes the data to be pushed to the target user terminal corresponding to the target user label.

And the confirming operation is used for confirming that the task information is correct and executing the data pushing task. Similar to the configuration operation, the determination operation may specifically be a touch operation, a cursor operation, a key operation, or a voice operation.

The data push task is the data push job assigned by the administrator to the cluster user. After receiving the data pushing task, the cluster user needs to push data according to the indication of the data pushing task.

The transit terminal refers to a terminal operated by a cluster user. The cluster user can be regarded as a transfer user for data pushing, and the cluster user only needs to perform simple task confirmation operation on the terminal, and the data to be pushed can be automatically sent to the terminal of the target user. The target user terminal is a terminal corresponding to the user identifier of the user label including the target user label. It can be understood that there may be at least one transit terminal, at least one target user terminal, and at least one management terminal.

Specifically, the administrator may perform confirmation of the push configuration information on the management terminal, thereby triggering generation of the data push task and transmission of the data push task. That is, the management terminal may generate a data push task based on the push configuration information in response to the confirmation operation of the push configuration information, and send the data push task to the relay terminal. After receiving the data pushing task, if the cluster user confirms to execute the data pushing task, the transfer terminal can respond to the confirmation operation for the data pushing task and automatically push the data to be pushed to the target user terminal corresponding to the target user tag. Therefore, each cluster user does not need to configure the data to be pushed and the target user corresponding to the data to be pushed respectively, and the cluster user can automatically push the data to be pushed to each target user at one time only by confirming the execution data pushing task on the transfer terminal.

In one embodiment, the push configuration information may further include a push time indicating a reference time for transmitting the data to be pushed to the target user terminal. The management terminal may send the data push task to the relay terminal according to the push time information, for example, when the push time is close to or reached, the data push task is sent to the relay terminal. Of course, the management terminal may also send the data push task to the relay terminal immediately after the data push task is generated. And if the transfer terminal confirms to execute the data pushing task, the transfer terminal actively waits until the pushing time is close to or reaches, and then sends the data to be pushed to the target user terminal.

In an embodiment, the management terminal may determine a target user identifier corresponding to a target user tag on the relay terminal, and send the data pushing task and the target user identifier to the relay terminal, so that the relay terminal only needs to directly send the data to be pushed to the target user terminal corresponding to the target user identifier. Certainly, the relay terminal may also autonomously determine the target user identifier, and after receiving the data pushing task, the relay terminal determines a local target user identifier based on the target user tag, and then sends the data to be pushed to the target user terminal corresponding to the target user identifier.

In one embodiment, in a vehicle-mounted application scenario, an administrator may configure a data pushing task on a vehicle-mounted terminal, and send the data pushing task to a relay terminal through the vehicle-mounted terminal. The cluster user can also receive the data pushing task through the vehicle-mounted terminal and display the data pushing task on the vehicle-mounted terminal. The cluster user can send the data to be pushed to the target user terminal through the vehicle-mounted terminal. The target user can also receive the data to be pushed through the vehicle-mounted terminal, and the data to be pushed is displayed on the vehicle-mounted terminal.

In the data pushing method, the management terminal responds to configuration operation of data pushing, displays pushing configuration information, responds to confirmation operation aiming at the pushing configuration information, generates a data pushing task based on the pushing configuration information, and sends the data pushing task to the transfer terminal. The push configuration information comprises data to be pushed and a target user tag, and the user tag is a tag configured for each user identifier by the first server based on the user behavior data in the target application. And after receiving the data pushing task, the transfer terminal responds to the confirmation operation aiming at the data pushing task and pushes the data to be pushed to the target user terminal corresponding to the target user label. The management terminal establishes the data pushing task in a unified mode, the transfer terminal can send the data to be pushed to the target user terminal in a one-key mode only through simple confirmation operation after receiving the data pushing task, manual selection of the data to be pushed and a data receiving party by the transfer terminal is not needed for data pushing, and data pushing efficiency is improved. In addition, the first server can automatically configure the user tag for the user identifier based on the user behavior data, so that when data pushing is carried out, a data receiving party does not need to be manually selected, the data receiving party can be quickly determined based on the target user tag, and the data pushing efficiency is further improved.

In one embodiment, before the configuration operation in response to the data push, the method further comprises:

responding to the starting operation of the management application, displaying a policy configuration interface, wherein the management application serves the associated application corresponding to the target application; determining a tag matching strategy in response to configuration operation triggered on a strategy configuration interface; the label matching strategy is used for carrying out label matching processing on the user behavior data corresponding to the current user identification and determining the user label corresponding to the current user identification.

Wherein the start-up operation is for starting up an application. Similar to the configuration operation, the start operation may specifically be a touch operation, a cursor operation, a key operation, or a voice operation.

The management application refers to a user cluster management application, the target application refers to an individual user communication application, and the associated application refers to a user cluster communication application. The management application serves the associated application, and the management application can provide additional services for the associated application, optimize and strengthen functions of the associated application. In one embodiment, the management application may be an application developed by a SaaS (Software as a Service) Service provider corresponding to the user cluster communication application. It is understood that the management application may be a web application, which is started through a web page, a desktop application, which is started through an icon, or an applet in an associated application, which is started through an icon.

The policy configuration interface is an interface for configuring a tag matching policy. The label matching strategy is used for carrying out label matching processing on the user behavior data corresponding to a certain user identification and determining the user label corresponding to the user identification. The current user identifier refers to any one of the user identifiers. The label matching strategy comprises a plurality of candidate labels and matching conditions corresponding to the candidate labels. And if the user behavior data meets any one matching condition, determining that the user label is a candidate label corresponding to the matching condition.

Specifically, after the administrator starts the management application on the management terminal, the administrator may enter a policy configuration interface and configure a tag matching policy on the policy configuration interface. The management terminal may first present a policy configuration interface to an administrator on the management terminal in response to an operation of the administrator to start the management application. Then, the management terminal may determine that the tag matches the policy in response to a configuration operation triggered by an administrator on the policy configuration interface. After the configuration is completed, the application server corresponding to the management application can perform tag matching processing on the user behavior data corresponding to the current user identifier based on the tag matching policy, so as to determine the user tag corresponding to the current user identifier.

Referring to fig. 3A, after the administrator logs in the management application, the management terminal may present an initialization interface of the management application. The initialization interface 302 is a tab selection area that includes a plurality of tab options, such as a "materials" management tab, a "tags management" tab, and a "tasks management" tab. 304 in the initialization interface is a tab content display area for displaying specific content of a certain tab. For example, the administrator clicks on the "tab manage" tab in 302, 304 may expose the policy configuration interface, the administrator clicks on the "task manage" tab in 302, and 304 may expose the push task configuration interface. It can be understood that after the administrator logs in the management application, the management terminal may automatically display the policy configuration interface, or the management terminal may respond to the trigger operation of the administrator on the tab "tab management" to display the policy configuration interface.

In one embodiment, since the management application serves the associated application corresponding to the target application, the administrator can log in to the management application through the associated application. For example, the administrator may "scan" the graphic code for logging in the management application through the graphic code collection portal after logging in the associated application, thereby logging in the management application. The graphic code is a graphic generated by encoding a character or a character string having a meaning expression function, and may include at least one of a barcode, a two-dimensional code, or an applet code. The administrator may also enter the management application through the applet portal of the management application after logging in the associated application.

In the above embodiment, the tag matching policy is configured in the management application, and the subsequent first server may perform data analysis on the user behavior data based on the tag matching policy, so as to configure the corresponding user tag for each user identifier.

In one embodiment, determining that the tag matches the policy in response to a configuration operation triggered at the policy configuration interface includes:

in a keyword tag configuration area of a strategy configuration interface, responding to configuration operation of a keyword tag, and displaying keyword tag configuration information, wherein the keyword tag configuration information comprises candidate tags and corresponding candidate keywords; responding to the confirmation operation aiming at the keyword tag configuration information, and generating a keyword matching strategy based on the keyword tag configuration information to obtain a tag matching strategy; the keyword matching strategy is used for determining that the user label corresponding to the current user identifier is a candidate label corresponding to the candidate keyword which is successfully matched when at least one historical conversation message in the user behavior data corresponding to the current user identifier is successfully matched with the candidate keyword.

The keyword tag configuration area is used for configuring a keyword matching strategy. The keyword matching strategy is used for performing label matching processing on historical conversation messages in the user behavior data of the current user identification, and determining a user label corresponding to the current user identification. Candidate tags configured in the keyword matching policy may be considered keyword tags. The keyword tag configuration information used for generating the keyword matching policy specifically includes candidate tags and candidate keywords corresponding to the candidate tags. The candidate tags refer to candidate user tags, the number of the candidate tags may be at least one, and the number of the candidate keywords corresponding to one candidate tag may be at least one.

The keyword tag configuration information comprises candidate tags and candidate keywords corresponding to the candidate tags, and therefore, the keyword matching strategy generated based on the keyword tag configuration information is used for determining that the user tag corresponding to the current user identifier is the candidate tag corresponding to the candidate keyword which is successfully matched when at least one historical conversation message in the user behavior data corresponding to the current user identifier is successfully matched with the candidate keyword. That is, the keyword matching policy is used to, when the message content of the historical conversation message triggers a candidate keyword, take the candidate tag corresponding to the triggered candidate keyword as the user tag corresponding to the current user identifier. It can be understood that the keyword tag configuration information may further include more information to further narrow the matching range and improve the accuracy of the user tag. For example, the keyword tag configuration information further includes a reference session type, which is a session type determined from candidate session types including a single person session type and a session group type. The single-person conversation type is used for determining that a user tag corresponding to a current user identifier is a candidate tag corresponding to a candidate keyword which is successfully matched when a history conversation message generated in a single-person chat conversation between the current individual user and the cluster user is successfully matched with the candidate keyword, and the conversation group type is used for determining that a user tag corresponding to a current user identifier is a candidate tag corresponding to a candidate keyword which is successfully matched when a history conversation message generated in a multi-person conversation between the current individual user and the cluster user is successfully matched with the candidate keyword.

Specifically, the tag matching policy may have multiple types of policies, and for improving the configuration efficiency and the subsequent matching efficiency, configuration areas corresponding to the types are displayed in the policy configuration interface for different types of policies, so that a user can perform policy configuration in a targeted manner.

The policy configuration interface comprises a keyword tag configuration area, and an administrator can configure information required by a keyword matching policy in the keyword tag configuration area and then start the configured keyword matching policy. In the keyword tag configuration area of the policy configuration interface, the management terminal may display the keyword tag configuration information configured by the administrator in response to the configuration operation of the administrator on the keyword tag. The management terminal can respond to the confirmation operation of the administrator on the keyword tag configuration information, generate a keyword matching strategy based on the keyword tag configuration information, and use the keyword matching strategy as a tag matching strategy. After the tag matching policy is obtained, the management terminal may send the tag matching policy to the first server and store the tag matching policy in the first server.

It is to be understood that, similarly to the configuration operation, the confirmation operation may specifically be a touch operation, a cursor operation, a key operation, or a voice operation. For example, the confirmation operation is a cursor click operation of the administrator to configure a control for "create" in the region for the keyword tag.

In the above embodiment, a keyword matching policy is configured in the keyword tag configuration area of the policy configuration interface, and the keyword matching policy may intelligently mine the user tags from the session messages of the individual users.

In one embodiment, the keyword tag configuration information further includes at least one of a reference keyword matching pattern and a reference transit user identifier corresponding to the candidate tag.

In a keyword tag configuration area of a policy configuration interface, displaying keyword tag configuration information in response to a configuration operation of a keyword tag, including:

determining a reference keyword matching pattern from the candidate keyword matching patterns in response to a configuration operation of the keyword matching patterns; the candidate keyword matching mode comprises a coarse-grained matching mode and a fine-grained matching mode, the coarse-grained matching mode is used for determining that the historical conversation message and the candidate keyword are successfully matched when the historical conversation message comprises the candidate keyword, and the fine-grained matching mode is used for determining that the historical conversation message and the candidate keyword are successfully matched when the historical conversation message is the candidate keyword.

Wherein the reference keyword matching pattern is a keyword matching pattern determined from the candidate keyword matching patterns. In performing the tag matching process, it may be determined whether the historical conversation message and the candidate keyword are successfully matched based on the reference keyword matching pattern. The candidate keyword matching patterns include a coarse-grained matching pattern and a fine-grained matching pattern. The coarse-grained matching pattern is a relatively coarse matching pattern, and the coarse-grained matching pattern is used for determining that the historical conversation message and the candidate keyword are successfully matched when the historical conversation message in the user behavior data comprises the candidate keyword, namely, the historical conversation message and the candidate keyword are considered to be successfully matched as long as the historical conversation message comprises the candidate keyword. Thus, coarse-grained matching patterns may also be considered fuzzy matching patterns. The fine-grained matching pattern is a relatively fine matching pattern, and the fine-grained matching pattern is used for determining that the historical conversation message is successfully matched with the candidate keyword when the historical conversation message is the candidate keyword, namely, the historical conversation message is determined to be successfully matched with the candidate keyword only if the historical conversation message is completely consistent with the candidate keyword. Thus, a fine-grained matching pattern may also be considered a precise matching pattern. For example, if the candidate keyword is "bmw", and the reference keyword matching pattern is a coarse-grained matching pattern, the history session messages successfully matched with the candidate keyword may be "bmw", and "bmw ride comfort". If the reference keyword matching pattern is a fine-grained matching pattern, the history session message successfully matched with the candidate keyword must be "bmw".

Specifically, the keyword tag configuration information may further include a reference keyword matching pattern corresponding to the candidate tag. The administrator can configure the reference keyword matching patterns corresponding to the candidate tags in the keyword tag configuration area. In the keyword tag configuration area, the management terminal may determine a reference keyword matching pattern configured by the administrator from the candidate keyword matching patterns in response to the configuration operation of the keyword matching pattern by the administrator. It is to be understood that, if the administrator does not configure the reference keyword matching pattern specifically, a default keyword matching pattern may be adopted when performing the tag matching process, and the default keyword matching pattern may be at least one of a coarse-grained matching pattern and a fine-grained matching pattern.

responding to the configuration operation of the transit user identification, and determining a reference transit user identification from the candidate transit user identifications; the reference relay user identifier is used for determining that the user tag corresponding to the current user identifier is the candidate tag corresponding to the candidate keyword which is successfully matched when the historical conversation message is successfully matched with the candidate keyword and the conversation user identifier corresponding to the historical conversation message comprises the target relay user identifier corresponding to the candidate keyword which is successfully matched.

Wherein the reference transit user identifier is at least one transit user identifier determined from the candidate transit user identifiers. The reference relay user identifier is used for determining that the user tag corresponding to the current user identifier is the candidate tag corresponding to the candidate keyword which is successfully matched when the historical conversation message is successfully matched with the candidate keyword and the conversation user identifier corresponding to the historical conversation message comprises the target relay user identifier corresponding to the candidate keyword which is successfully matched. That is, it is not only necessary that the history session message is successfully matched with the candidate keyword, but also that the session object corresponding to the history session message includes the reference transit user identifier, so as to determine that the user tag is the candidate tag corresponding to the candidate keyword that is successfully matched. When the individual user triggers the candidate keyword in the chat process with the specific cluster user, the corresponding keyword tag is configured for the individual user.

Specifically, the keyword tag configuration information may further include a reference transit user identifier. The administrator can configure the reference transit user identifier corresponding to the candidate tag in the keyword tag configuration area. In the keyword tag configuration area, the management terminal may determine the reference relay user identifier from the candidate relay user identifiers in response to a configuration operation of the relay user identifier by the administrator.

Referring to fig. 3B, the management terminal presents the policy configuration interface in response to the trigger operation of the administrator on the "auto tab" in the pull-down option of the "tab management" tab. The policy configuration interface also comprises a tab selection area, wherein the tab selection area comprises an 'automatic label library' tab, a 'keyword label' tab, a 'group-entering behavior label' tab and an 'interactive behavior label' tab. And the management terminal responds to the triggering operation of the administrator on the 'key word label' page label and displays the key word label configuration area. The administrator can configure the name of the policy in the "labeling rule name" area, so as to quickly find the corresponding policy based on the policy name in the following. The administrator can configure candidate tags in the "tag name" area and configure tag groups into which the candidate tags belong in the "belonging tag group" area, so that the candidate tags can be grouped, managed and searched in the following. The administrator can configure a candidate keyword corresponding to the candidate tag in the "fuzzy matching keyword" area, and a reference keyword matching pattern corresponding to the candidate keyword is a coarse-grained matching pattern. The administrator can configure candidate keywords corresponding to the candidate tags in the "precise matching keyword" area, and the reference keyword matching mode corresponding to the candidate keywords is a fine-grained matching mode. The administrator can configure the reference transit user id in the "applicable membership range" area. After the information configuration is completed, the management terminal may respond to a click operation of an administrator on the "create" control, and generate a keyword matching policy based on the keyword tag configuration information displayed in the keyword tag configuration area. It will be appreciated that other information may also be included in the keyword tag configuration area, such as a "remarks" area for introducing keyword matching policies, a "session type" area for determining a reference session type, and the like.

In the above embodiment, the keyword tag configuration information further includes at least one of a reference keyword matching pattern corresponding to the candidate tag and a reference transit user identifier, and a keyword matching policy generated by the keyword tag configuration information with richer information can more accurately mine the user tag from the session message of the individual user, thereby facilitating further refinement of the individual user and improving validity and accuracy of pushing.

in a group entry behavior tag configuration area of a strategy configuration interface, responding to configuration operation of a group entry behavior tag, and displaying group entry behavior tag configuration information, wherein the group entry behavior tag configuration information comprises candidate tags and corresponding candidate session identifications; responding to the confirmation operation aiming at the configuration information of the group entry behavior tags, and generating a group entry behavior matching strategy based on the configuration information of the group entry behavior tags to obtain a tag matching strategy; the matching strategy of the group-entering behavior is used for determining that the user label corresponding to the current user identification is the candidate label corresponding to the candidate session identification which is successfully matched when the target session identification is successfully matched with the candidate session identification, and the target session identification is the session identification corresponding to the target group-entering behavior in the user behavior data corresponding to the current user identification.

The group behavior tag configuration area is used for configuring a group behavior matching strategy. And the group entry behavior matching strategy is used for performing label matching processing on the target group entry behavior in the user behavior data of the current user identification and determining the user label corresponding to the current user identification. The group entry behavior refers to the behavior of an individual user to join a session group. A user may join a session group actively, for example, the user joins the session group by scanning a group two-dimensional code, or the user may join passively, for example, the user is invited to join the session group by an existing user in the session group. Candidate tags configured in the grouping behavior matching policy may be considered as grouping behavior tags. The grouping behavior tag configuration information used for generating the grouping behavior matching policy specifically includes candidate tags and candidate session identifications corresponding to the candidate tags. The candidate tags may be at least one, and the candidate session identifier corresponding to one candidate tag may be at least one.

The configuration information of the group entry behavior tag comprises a candidate tag and a corresponding candidate session identifier, so that the group entry behavior matching strategy generated based on the configuration information of the group entry behavior tag is used for determining that the user tag corresponding to the current user identifier is the candidate tag corresponding to the candidate session identifier which is successfully matched when the target session identifier corresponding to the target group entry behavior is successfully matched with the candidate session identifier in the user behavior data corresponding to the current user identifier. That is, the matching policy of the group entry behavior is used to take the candidate tag matched with the target session identifier corresponding to the target session group as the user tag corresponding to the current user identifier when the current individual user joins the target session group created by the cluster user. And when the individual user joins the specific session group, configuring a corresponding group entering behavior tag for the individual user.

Specifically, the policy configuration interface may further include a group entry behavior tag configuration area, and the administrator may configure information required by the group entry behavior matching policy in the group entry behavior tag configuration area, and then enable the configured group entry behavior matching policy. In the group entry behavior tag configuration area of the policy configuration interface, the management terminal may display the group entry behavior tag configuration information configured by the administrator in response to the configuration operation of the administrator on the group entry behavior tag. The management terminal can respond to the confirmation operation of the administrator on the configuration information of the group entry behavior tags, generate a group entry behavior matching strategy based on the configuration information of the group entry behavior tags, and use the group entry behavior matching strategy as the tag matching strategy.

Referring to fig. 3C, the management terminal displays the grouping behavior tag configuration area in response to a trigger operation of the administrator on the "grouping behavior tag" tab. The administrator can configure the name of the policy in the "tagging rule name" area, configure the candidate tag in the "tag name" area, configure the tag group into which the candidate tag is put in the "belonging tag group" area, and configure the candidate session identifier corresponding to the candidate tag in the "specified group chat" area. After the information configuration is completed, the management terminal can respond to the clicking operation of the administrator on the 'creation' control, and generate the grouping behavior matching strategy based on the grouping behavior tag configuration information displayed in the grouping behavior tag configuration area. It is to be understood that the group entry behavior tag configuration area may further include other information, for example, an "assigned group entry manner" area for determining a reference group entry manner, an "assigned member range" area for determining an invitation relay user identifier, and the like. And if the individual user joining the specific session group is invited by the appointed cluster user, taking the candidate label corresponding to the characteristic session group as the user label of the individual user.

In the above embodiment, the grouping behavior matching policy is configured in the grouping behavior tag configuration area of the policy configuration interface, and the grouping behavior matching policy may intelligently mine the user tags from the grouping information of the individual users.

In one embodiment, the grouping behavior tag configuration information further includes a reference grouping manner corresponding to the candidate tag. In a group entry behavior tag configuration area of a policy configuration interface, responding to configuration operation of a group entry behavior tag, and displaying group entry behavior tag configuration information, wherein the method comprises the following steps:

responding to the configuration operation of the group entering mode, and determining to refer to the group entering mode; and the reference group entering mode is used for determining that the user label corresponding to the current user identification is the corresponding candidate label when the group entering mode corresponding to the target group entering behavior is also successfully matched with the reference group entering mode corresponding to the successfully matched candidate session identification.

The group entering mode refers to a mode that a user joins a session group, and includes active group entering and passive group entering. Different candidate tags can be configured according to different group entering modes of joining the same session group so as to refine user behaviors. The reference clustering scheme is a clustering scheme determined from the candidate clustering schemes. And the reference group entering mode is used for determining that the user label corresponding to the current user identification is the corresponding candidate label when the group entering mode corresponding to the target group entering behavior of the current individual user is also successfully matched with the reference group entering mode corresponding to the successfully matched candidate session identification. That is, the user tag is determined to be the candidate tag corresponding to the successfully matched candidate session identifier only when the target session identifier corresponding to the target grouping behavior is required to be matched with the candidate session identifier and the grouping mode corresponding to the target grouping behavior is required to be matched with the reference grouping mode corresponding to the candidate session identifier. When an individual user joins a specific session group in a specific manner, a corresponding group entry behavior tag is configured for the individual user.

Specifically, the grouping behavior tag configuration information may further include a reference grouping manner corresponding to the candidate tag. The administrator can configure a reference clustering mode corresponding to the candidate tag in the clustering behavior tag configuration area. In the group entry behavior tag configuration area, the management terminal may determine a reference group entry manner from the candidate group entry manners in response to a configuration operation of an administrator on the group entry manner. It is to be understood that, if the administrator does not configure the reference grouping manner specifically, a default grouping manner may be adopted when performing the tag matching process, and the default grouping manner may be at least one of active grouping and passive grouping.

In the above embodiment, the grouping behavior tag configuration information further includes a reference grouping manner corresponding to the candidate tag, and a grouping behavior matching policy generated by the grouping behavior tag configuration information with richer information can more accurately mine the user tag from the session message of the individual user, thereby facilitating further refinement of the individual user and improving validity and accuracy of pushing.

In one embodiment, before determining that the tag matches the policy in response to the configuration operation triggered at the policy configuration interface, the method further comprises:

displaying a data uploading interface; and uploading a plurality of candidate push data in a data uploading interface.

The data uploading interface is used for uploading candidate pushing data, and the candidate pushing data can be used for data pushing and can also be used for configuring a tag matching strategy. The administrator can upload a plurality of candidate push data on a data uploading interface of the management application and store the candidate push data to the first server.

Responding to configuration operation triggered on a policy configuration interface, and determining a tag matching policy comprises the following steps:

in an interaction behavior tag configuration area of a strategy configuration interface, responding to configuration operation of an interaction behavior tag, and displaying interaction behavior tag configuration information, wherein the interaction behavior tag configuration information comprises candidate tags, corresponding candidate push data and candidate interaction behavior information; responding to the confirmation operation aiming at the interactive behavior tag configuration information, and generating an interactive behavior matching strategy based on the interactive behavior tag configuration information to obtain a tag matching strategy; the interaction behavior matching strategy is used for determining that the user tag corresponding to the current user identifier is the candidate tag corresponding to the candidate push data which is successfully matched when the push data corresponding to the target interaction behavior is successfully matched with the candidate push data and the interaction behavior information corresponding to the target interaction behavior is also successfully matched with the candidate interaction behavior information corresponding to the candidate push data which is successfully matched, and the target interaction behavior is acquired from the user behavior data corresponding to the current user identifier.

The interactive behavior tag configuration area is used for configuring an interactive behavior matching strategy. And the interactive behavior matching strategy is used for performing label matching processing on the target interactive behavior in the user behavior data of the current user identification and determining the user label corresponding to the current user identification. The interactive behavior refers to an interactive behavior of an individual user on the push data sent by the cluster user, and may specifically include behaviors of clicking, praise, comment, forwarding and the like on the push data, for example. The interaction behavior information refers to detailed information of the interaction behavior, and may specifically include information such as interaction times, interaction time, and interaction type. The candidate tags configured in the interaction behavior matching strategy can be regarded as interaction behavior tags or material interaction tags. The interaction behavior tag configuration information used for generating the interaction behavior matching policy specifically includes a candidate tag, candidate push data corresponding to the candidate tag, and candidate interaction behavior information. The candidate tags may be at least one, and the candidate push data corresponding to one candidate tag may be at least one.

The interaction behavior tag configuration information comprises candidate tags, candidate push data corresponding to the candidate tags and candidate interaction behavior information, and therefore, an interaction behavior matching strategy generated based on the interaction behavior tag configuration information is used for successfully matching the push data corresponding to the target interaction behavior with the candidate push data in the user behavior data corresponding to the current user identifier, and when the interaction behavior information corresponding to the target interaction behavior is successfully matched with the candidate interaction behavior information corresponding to the candidate push data successfully matched, the user tag corresponding to the current user identifier is determined to be the candidate tag corresponding to the candidate push data successfully matched. That is, the interaction behavior matching policy is used to configure a corresponding interaction behavior tag for the individual user when the current individual user satisfies an interaction condition with respect to the interaction behavior of the push data sent by the cluster user. For example, within 60 days after the individual user receives the push data a, if the individual user clicks the push data a 2 times or more in an accumulated manner, the individual user is marked with an interactive behavior tag corresponding to the push data a.

Specifically, the policy configuration interface may further include an interaction behavior tag configuration area, and the administrator may configure information required by the interaction behavior matching policy in the interaction behavior tag configuration area and then enable the configured interaction behavior matching policy. In the interaction behavior tag configuration area of the policy configuration interface, the management terminal can respond to the configuration operation of the administrator on the interaction behavior tag and display the interaction behavior tag configuration information configured by the administrator. The management terminal can respond to the confirmation operation of the administrator on the interactive behavior tag configuration information, generates an interactive behavior matching strategy based on the interactive behavior tag configuration information, and takes the interactive behavior matching strategy as a tag matching strategy.

Referring to fig. 3D, the management terminal displays the interactive behavior tag configuration area in response to a trigger operation of the administrator on the "interactive behavior tag" tab. The administrator can configure the name of the policy in the "tagging rule name" area, configure the candidate tag in the "tag name" area, and configure the tag group into which the candidate tag is put in the "belonging tag group" area. The administrator can select candidate push data corresponding to the candidate tags from the uploaded candidate push data in the specified material area, and can also configure the candidate push data corresponding to the candidate tags by uploading new candidate push data in the added material area. The administrator can configure candidate interaction behavior information corresponding to the candidate tags in the 'rule specification' area. After the information configuration is completed, the management terminal can respond to the clicking operation of the administrator on the 'creation' control, and generates an interactive behavior matching strategy based on the interactive behavior tag configuration information displayed in the interactive behavior tag configuration area. It is understood that other information may also be included in the interactive behavior tag configuration area, for example, a "specified member range" area for determining the push relay user identifier, and the like. And if the appointed push data browsed by the individual user is sent by the appointed cluster user and the interaction behavior information of the individual user meets the interaction condition, taking the candidate tag corresponding to the appointed push data as the user tag of the individual user. In addition, the data uploading interface can be in an independent interface, and can also be in the same interface with the interactive behavior tag configuration area.

In the above embodiment, the interactive behavior matching policy is configured in the interactive behavior tag configuration area of the policy configuration interface, and the interactive behavior matching policy may intelligently mine the user tags from the material interaction messages of the individual users.

displaying a push task configuration interface; determining data to be pushed in response to a push data selection operation triggered on a push task configuration interface; and determining a target user tag in response to a user tag selection operation triggered on the push task configuration interface.

In particular, an administrator may configure push configuration information on a push task configuration interface of the management application. After entering the management application, the management terminal may show a push task configuration interface to an administrator, and the management terminal may determine, in response to a push data selection operation triggered by the administrator on the push task configuration interface, data to be pushed from the candidate push data set, determine, in response to a user tag selection operation triggered by the administrator on the push task configuration interface, a target user tag from the candidate tag set, and further take the data to be pushed and the target user tag as push configuration information.

In the above embodiment, the push configuration information can be rapidly configured through the selection operation triggered on the push task configuration interface.

In one embodiment, the push configuration information further includes at least one of a target push manner and a target transit user identifier.

Responding to the configuration operation of data push, displaying push configuration information, comprising: responding to a transit user identifier selection operation triggered on a push task configuration interface, and determining a target transit user identifier; the transfer terminal is a user terminal corresponding to the target transfer user identifier.

Specifically, the target transit user identifier refers to a user identifier corresponding to a cluster user that receives the data push task. When the push configuration information is configured, the management terminal may further determine a target relay user identifier from the candidate relay user identifiers in response to a relay user identifier selection operation triggered by an administrator on the push task configuration interface, so that after a data push task is subsequently generated, the management terminal may use a user terminal corresponding to the target relay user identifier as a relay terminal and send the data push task to the relay terminal. It can be understood that, if the administrator does not specially configure the target relay user identifier, the data push task may be sent to a default relay terminal by default, where the default relay terminal may be a user terminal corresponding to all cluster users, or may be a user terminal corresponding to a preset specific cluster user.

Responding to the configuration operation of data push, displaying push configuration information, comprising: and determining a target pushing mode in response to a pushing mode selection operation triggered on the pushing task configuration interface.

Specifically, the target push mode refers to a mode in which the relay terminal pushes data, and includes at least one of a session push mode and a dynamic information push mode. When the push configuration information is configured, the management terminal can also respond to a push mode selection operation triggered by an administrator on a push task configuration interface, and a target push mode is determined from the candidate push modes, so that the subsequent transfer terminal can send the data to be pushed to the target user terminal according to the target push mode after receiving the data push task.

Referring to fig. 4, the management terminal displays a push task configuration interface in response to a trigger operation of the administrator on "new task" in the pull-down option of the "task management" tab. The administrator can push the name of the task in the "task name" area configuration data and relay the user identification in the "executive member" area configuration target. When the administrator selects the option of "all employees", the target transit user identifier is the user identifier corresponding to all the cluster users. When the administrator selects the 'appointed staff' option, the push task configuration interface can further display an 'add executive staff' control, if the administrator triggers the 'add executive staff' control, a 'add executive staff' popup is displayed on the push task configuration interface, and the administrator can configure a target transfer user identifier in the popup. The administrator can configure a target pushing mode in a sending type area, configure the sending time of a pushing task in a sending time area, and configure a target user tag in a sending range area. When the administrator selects the 'all' option, the target user tags are all the user tags, when the administrator selects the 'appointed tag' option, the pushing task configuration interface further displays a 'selection' control, if the administrator triggers the 'selection' control, a 'selection user tag' popup is displayed on the pushing task configuration interface, and the administrator can configure the target user tags in the popup. The method comprises the steps that an administrator can configure data to be pushed in a data to be pushed area, the administrator can determine a target type in the data types, so that grouping conditions of candidate pushed data corresponding to the target type are displayed on an interface, then the administrator determines a target group from the grouping conditions, so that schematic diagrams of the candidate pushed data contained in the target group are displayed on the interface, and finally the administrator determines the data to be pushed from the displayed schematic diagrams. After the information configuration is completed, the management terminal can respond to the clicking operation of the administrator on the completion control, and generates a data pushing task based on the pushing configuration information.

It is understood that, referring to fig. 5A, the administrator may determine a target push mode in the drop-down option of the "task management" tab, and then configure other information in the push task configuration interface corresponding to the target push mode. Referring to fig. 5B, the administrator may also determine a target push manner in the tab selection area of the push task configuration interface, and then configure other information in the configuration area corresponding to the target push manner.

In the above embodiment, the push configuration information further includes at least one of a target push mode and a target relay user identifier, and a data push task generated by the push configuration information with richer information can implement more accurate and more effective data push.

In an embodiment, when the target push mode is a session push mode, the target push mode is used to push data to be pushed to a target session interface as a target session message, and the target session interface is a session interface of the relay terminal and the target user terminal in an associated application corresponding to the target application.

Specifically, the session pushing mode is used for performing data pushing by using data to be pushed as a target session message, and sending the data to be pushed to a session interface between the cluster user and the individual user. If the target pushing mode is a session pushing mode, the transfer terminal can push the data to be pushed to a target session interface as a target session message, wherein the target session interface refers to a session interface between the transfer terminal and the target user terminal in the associated application corresponding to the target application. It is to be understood that the target conversation interface may be a single person conversation interface or a conversation group interface.

In an embodiment, after the transit terminal confirms to execute the data pushing task, a session group may be automatically established first, each individual user corresponding to the target user tag is automatically pulled into the session group, and then the data to be pushed is automatically sent to the session group as the target session message. Therefore, the session group is established first and then data pushing is carried out, so that the pushing pressure of the transfer terminal can be reduced, and the effect of sending the data to be pushed to a plurality of user terminals can be realized by the transfer terminal only needing one-time data pushing.

In the above embodiment, the conversation chat is an efficient information exchange manner, and data to be pushed is used as a target conversation message for data pushing, so that the effectiveness of data pushing can be improved.

In one embodiment, when the target pushing mode is a dynamic information pushing mode, the target pushing mode is used for sending data to be pushed to the target user terminal as target dynamic information, so that the target user terminal displays the target dynamic information on a dynamic information display interface in the target application.

Specifically, the dynamic information pushing mode is used for performing data pushing by using data to be pushed as target dynamic information, and sending the data to be pushed to a dynamic information display interface of an individual user. The dynamic information presentation interface is used to publish personal dynamics, for example, the dynamic information presentation interface may be a circle of friends. The dynamic information display interface of a user displays the dynamic information sent by the user and the dynamic information sent by each friend of the user. If the target pushing mode is a dynamic information pushing mode, the transfer terminal can send the data to be pushed to the target user terminal as the target dynamic information, so that the target user terminal can display the target dynamic information on a dynamic information display interface in the target application. The target user can directly comment and like the displayed target dynamic information on the dynamic information display interface.

In the above embodiment, browsing the dynamic information is an efficient information exchange manner, and data push is performed by using the data to be pushed as target dynamic information, so that the effectiveness of data push can be improved.

In an embodiment, as shown in fig. 6, a data pushing method is provided, which is described by taking an example that the method is applied to the transit terminal in fig. 1, and includes the following steps:

step S602, displaying a data pushing task sent by the management terminal; the data pushing task is generated by the management terminal based on pushing configuration information in response to a confirmation operation aiming at the pushing configuration information, the pushing configuration information is obtained by the management terminal in response to a configuration operation of data pushing, and the pushing configuration information comprises data to be pushed and a target user label.

Step S604, in response to the confirmation operation for the data pushing task, pushing the data to be pushed to the target user terminal corresponding to the target user tag.

Specifically, after the management terminal generates a data pushing task based on the relevant operations of the administrator, the data pushing task is sent to the transfer terminal. And after the transfer terminal of the cluster user receives the data pushing task, the data pushing task can be displayed. And if the cluster user determines to execute the data pushing task, the transfer terminal responds to the confirmation operation of the cluster user for the data pushing task and automatically sends the data to be pushed to the target user terminal corresponding to the target user label. Therefore, each cluster user does not need to configure the data to be pushed and the target user corresponding to the data to be pushed respectively, and the cluster user can automatically push the data to be pushed to the target user only by confirming the execution data pushing task on the transfer terminal.

It is to be understood that the specific processes of the management terminal and the first server for data processing may refer to the methods described in the respective related embodiments.

According to the data pushing method, the management terminal establishes the data pushing tasks in a unified mode, the transfer terminal can send the data to be pushed to the target user terminal in a one-key mode only through simple confirmation operation after receiving the data pushing tasks, manual selection of the data to be pushed and a data receiving party by the transfer terminal is not needed for data pushing, and data pushing efficiency is improved. In addition, the first server can automatically configure the user tag for the user identifier based on the user behavior data, so that when data pushing is carried out, a data receiving party does not need to be manually selected, the data receiving party can be quickly determined based on the target user tag, and the data pushing efficiency is further improved.

In one embodiment, the data pushing task sent by the display management terminal includes:

responding to the starting operation of the associated application corresponding to the target application, and displaying a session management interface, wherein the session management interface displays a session entrance of a management session interface of a transit terminal and a management terminal; responding to a trigger operation aiming at a session entrance, and entering a management session interface; and displaying the data pushing task in the management session interface.

The session management interface is used for displaying session entries of each session interface of the cluster user in the associated application, so that the session management interface displays the session entries of the session interfaces of the cluster user and the administrator. The management session interface is a session interface of the transit terminal and the management terminal in the associated application, that is, a session interface of the cluster user and the administrator in the associated application.

Specifically, after the cluster user starts the associated application on the transit terminal, the cluster user may enter a session management interface, and the cluster user may trigger entering of a session interface with an administrator on the session management interface. The transit terminal can respond to the starting operation of the cluster user on the associated application, and firstly displays a session management interface to the cluster user. Once the transit terminal receives the data pushing task, a session entrance for managing the session interface in the session management interface has a message prompt to prompt the cluster user to receive a new message sent by an administrator. Then, the transit terminal may enter a session interface with an administrator in response to a triggering operation of the cluster user for a session entry of the management session interface, and display a data push task on the management session interface.

Referring to fig. 7A, (a) in fig. 7A is a session management interface showing a session entry having a plurality of session interfaces. The target application is displayed in a session entrance of a session interface of the user B in the session management interface, and the target application indicates that the user B is an individual user and is not a user in the user cluster. The 'r' is displayed on a session entry of the session interface of the administrator in the session management interface, which indicates that a new message sent by the administrator is received, and the message is not browsed currently. The cluster user clicks on the session entry of the session interface with the administrator, and can enter the session interface with the administrator, as shown in (b) of fig. 7A. When the cluster user clicks any one data pushing task, the cluster user can jump to a detail display interface of the data pushing task, where the detail display interface is shown in (c) of fig. 7A. In the detail display interface, the cluster user may view detailed information of the data pushing task, for example, information such as data to be pushed, a target user tag, a target user identifier, and the like. The cluster user clicks the sending control to trigger sending of the data to be pushed to the target user terminal.

In the above embodiment, the conversation chat is an efficient information exchange manner, and the data push task is displayed in the conversation interface between the cluster user and the administrator, so that the execution of the data push task is accelerated, and the push efficiency is improved.

In one embodiment, the method further comprises:

responding to session sharing operation aiming at data to be pushed, and displaying a session sharing configuration interface, wherein the session sharing configuration interface comprises a user tag configuration area; displaying a target user tag in response to a configuration operation for the user tag configuration area; and responding to the sharing confirmation operation aiming at the data to be pushed, sending the data to be pushed as a target session message to a target session interface, wherein the target session interface is a session interface of the transfer terminal and the target user terminal in the associated application corresponding to the target application.

Specifically, in addition to performing data pushing according to the received data pushing task, the relay terminal may also perform data pushing autonomously based on the target user tag. When data pushing is performed based on the target user tag, data to be pushed can be used as a session message for data pushing. The transit terminal can respond to the session sharing operation of the cluster user for the data to be pushed in the associated application, and displays a session sharing configuration interface for the cluster user. The session sharing configuration interface comprises a user tag configuration area, and the cluster user can configure a target user tag in the user tag configuration area. The transit terminal can respond to the configuration operation of the cluster user for the user tag configuration area, determine a target user tag from the candidate tag set, and display the target user tag. The relay terminal can respond to the sharing confirmation operation of the cluster user for the data to be pushed, and sends the data to be pushed as a target session message to a target session interface of the relay user and an individual user.

Referring to fig. 7B, (a) in fig. 7B is a conversation interface of the cluster user and the user a. The cluster user may use the session message "car picture" sent by user a as the data to be pushed. When the cluster user presses the conversation message "car picture" for a long time, the operation controls such as "copy", "forward", "save", and the like are displayed, and when the cluster user clicks the "forward" control, the conversation sharing configuration interface is displayed, and the conversation sharing configuration interface refers to (B) in fig. 7B. When the cluster user clicks the "filter according to tag" area, the cluster user enters the user tag configuration area, and the user tag configuration area refers to (c) in fig. 7B. The user tag configuration area can display user tags in groups, including a keyword tag group, an entering behavior tag group and a material interaction tag group. The clustered users may select at least one user tag therefrom as a target user tag. After the target user tag is determined, session sharing confirmation information of the data to be pushed is shown to the cluster user, referring to (d) in fig. 7B. When the cluster user clicks the sending control, the transfer terminal sends the data to be pushed, namely the automobile pictures, to each target session interface corresponding to the target user label at one time. Therefore, the transfer terminal can realize batched data pushing based on the target user label, and the pushing efficiency is improved.

In one embodiment, in order to improve the security of the target user tag and avoid misuse of the target user tag, an administrator may set a part of the cluster users to have user tag operation authority. The cluster user with the user tag operation authority can check the user tag of the individual user on the transfer terminal, and then data pushing is carried out based on the user tag of the individual user.

In the above embodiment, in addition to performing data pushing according to the received data pushing task, the relay terminal may also perform data pushing autonomously based on the target user tag. When session messages are shared, the transfer terminal can simultaneously push data to a plurality of users at one time based on the target user tags, and the pushing efficiency is improved.

In one embodiment, the method further comprises:

responding to the dynamic information sharing operation aiming at the data to be pushed, and displaying a dynamic information sharing configuration interface; the dynamic information sharing configuration interface comprises a user tag configuration area; displaying a target user tag in response to a configuration operation for the user tag configuration area; and responding to the sharing confirmation operation aiming at the data to be pushed, sending the data to be pushed as target dynamic information to the target user terminal, and displaying the target dynamic information on a dynamic information display interface of the target application at the target user terminal.

Specifically, when data pushing is performed based on the target user tag, in addition to performing data pushing by using data to be pushed as a session message, data pushing may also be performed by using data to be pushed as dynamic information. The relay terminal can respond to the dynamic information sharing operation of the cluster user for the data to be pushed in the associated application, and displays a dynamic information sharing configuration interface for the cluster user. The dynamic information sharing configuration interface comprises a user tag configuration area, and the cluster user can configure a target user tag in the user tag configuration area. The transit terminal can respond to the configuration operation of the cluster user for the user tag configuration area, determine a target user tag from the candidate tag set, and display the target user tag. The transfer terminal can respond to sharing confirmation operation of the cluster user for the data to be pushed, and sends the data to be pushed as target dynamic information to the target user terminal, so that the data to be pushed is displayed on a dynamic information display interface of an individual user.

Referring to fig. 7C, fig. 7C (a) is a dynamic information sharing configuration interface, and a cluster user may input data to be pushed in a sharing content configuration area of the dynamic information sharing configuration interface. When the cluster user clicks the "visible user" area, the user tag configuration area is entered, and the user tag configuration area refers to (b) of fig. 7C. The clustered users may select at least one user tag therefrom as a target user tag. And when the cluster user clicks the 'confirmation' control, returning to the dynamic information sharing configuration interface. When the cluster user clicks the 'issuing' control, the transfer terminal issues the data to be pushed as target dynamic information to the dynamic information configuration interface, and the browsable user of the data to be pushed is each individual user corresponding to the target user label.

In the above embodiment, in addition to performing data pushing according to the received data pushing task, the relay terminal may also perform data pushing autonomously based on the target user tag. When dynamic information sharing is carried out, the transfer terminal can simultaneously carry out data pushing on a plurality of users at one time based on the target user tags, and pushing efficiency is improved.

In one embodiment, the method further comprises:

displaying a session creation interface; the session creation interface comprises a user tag configuration area; determining a target user tag in response to a configuration operation for the user tag configuration area; responding to the creation operation of the session group, establishing a target session group corresponding to the target user label, generating group-entering invitation information corresponding to the target session group, and sending the group-entering invitation information to a target session interface, wherein the target session interface is a session interface of the relay terminal and the target user terminal in an associated application corresponding to the target application.

Specifically, in addition to pushing data based on the target user tag, the relay terminal may also create a session group based on the target user tag, and establish an exclusive session group for each individual user corresponding to the same target user tag. The clustered user may create a new session group in a session creation interface of the associated application. The transit terminal displays a session creation interface to the cluster user, the session creation interface comprises a user tag configuration area, and the cluster user can configure a target user tag in the user tag configuration area. The transfer terminal responds to configuration operation of the cluster user for the user tag configuration area, determines a target user tag from the candidate tag set, responds to creation operation of the cluster user for the session group, establishes a target session group corresponding to the target user tag, generates group entry invitation information corresponding to the target session group, and sends the group entry invitation information to a target session interface of the cluster user and an individual user corresponding to the target user tag in the associated application. After receiving the group invitation information, each target individual user can join the target session group based on the group invitation information. For example, the group invitation information may specifically be a group invitation two-dimensional code, and after receiving the group invitation two-dimensional code, the target individual user may join the target session group by scanning the group invitation two-dimensional code.

In the above embodiment, in addition to performing data push based on the target user tag, the relay terminal may also create a session group based on the target user tag. When the session group is created, the transit terminal can simultaneously send group invitation information to a plurality of users at one time based on the target user label, so that the creation efficiency of the session group is improved.

In one embodiment, the method further comprises:

displaying behavior track data corresponding to the current user identification in a user information display interface corresponding to the current user identification; the behavior trace data is trace data obtained by performing behavior arrangement on user behavior data corresponding to the current user identifier.

Specifically, the user information presentation interface is used for presenting basic information of the user, for example, data such as an avatar, a name, tag information, behavior information, and the like of the user. The transfer terminal can respond to the triggering operation of the cluster user for the head portrait of the individual user and display a user information display interface corresponding to the individual user. In addition to displaying some conventional information, behavior track data corresponding to the current user identifier can be displayed in a user information display interface corresponding to the current user identifier, so that the cluster user can quickly know information exchange conditions between the current individual user and the user cluster, quickly know interest points and attention points of the current individual user, and accordingly data push can be performed on the individual user in a targeted manner. The behavior track data is obtained by the first server performing behavior arrangement on the user behavior data corresponding to the current user identifier. The first server may specifically extract the user behavior matched with the candidate tag from the user behavior data, and sort the extracted user behavior according to a time sequence to obtain the behavior trajectory data. The first server may also extract a preset type of user behavior from the user behavior data, and sort the extracted user behavior according to a time sequence to obtain behavior trajectory data. It is understood that the preset type can be set according to the requirement, for example, an approval behavior, a forwarding behavior, and the like. The behavior trace data may be presented in a time axis manner or in a graph manner.

Referring to fig. 8, the clustered users click on the individual user avatar, and may enter the user information presentation interface. When the cluster user clicks the "tag information" area, all user tags of the individual users are displayed on the user information display interface, including tags manually set by human and tags automatically configured based on the user behavior data, refer to (a) in fig. 8. When the cluster user clicks the "behavior information" area, the behavior trace data of the individual user is displayed on the user information display interface, referring to (b) in fig. 8.

In the embodiment, the behavior track data is displayed for the cluster users in the user information display interface, so that interest points of the individual users can be intuitively known, and accurate pushing of the individual users is facilitated.

In one embodiment, as shown in fig. 9, a tag processing method is provided, which is exemplified by the application of the method to the first server in fig. 1, and includes the following steps:

step S902, obtaining user behavior data corresponding to each user identifier in the target application.

Step S904, determining user tags corresponding to the user identifiers based on the user behavior data, and forming a candidate tag set.

Specifically, the first server may obtain user behavior data of each individual user in the target application from the terminal and the server, perform data analysis on the user behavior data based on a certain algorithm and a certain policy, and determine a user tag corresponding to the individual user, thereby configuring the corresponding user tag for the individual user. The first server can form a candidate label set by the user labels and send the candidate label set to the management terminal. It can be understood that the first server may obtain user behavior data corresponding to the individual user from the mass data based on the user identifier of the individual user.

In an embodiment, after the user behavior data is obtained, the first server may directly perform data analysis on the user behavior data to determine the user tag corresponding to the individual user. The first server may also pre-process the user behavior data, filter out redundant information, store the pre-processed user behavior data in a message queue, and subsequently read the user behavior data from the message queue for data analysis, thereby determining the user tag corresponding to the individual user. The introduction of the message queue can decouple the tag processing process and improve the stability of data processing.

Step S906, sending the candidate label set to a management terminal so that the management terminal can display the candidate label set on a pushing task configuration interface and determine a target user label from the candidate label set; the target user tag is used for data pushing, a data pushing process is that the management terminal sends a data pushing task to the transfer terminal so that the transfer terminal responds to a confirmation operation for the data pushing task and pushes data to be pushed to the target user terminal corresponding to the target user tag, the data pushing task is generated based on pushing configuration information, and the pushing configuration information comprises the data to be pushed and the target user tag.

Specifically, after the first server sends the candidate tag set to the management terminal, the management terminal may display the candidate tag set on the push task configuration interface, so that an administrator determines the target user tag from the candidate tag set when configuring the push configuration information. The management terminal can respond to configuration operation of an administrator on data pushing, display pushing configuration information, the pushing configuration information comprises data to be pushed and a target user label, and then respond to confirmation operation of the administrator on the pushing configuration information, and generate a data pushing task based on the pushing configuration information. The management terminal sends the data pushing task to the transfer terminal, and the transfer terminal can respond to the confirmation operation of the cluster user for the data pushing task and push the data to be pushed to the target user terminal corresponding to the target user label.

It is to be understood that the specific data processing procedures of the management terminal and the transit terminal may refer to the methods described in the foregoing respective related embodiments.

In the tag processing method, the first server can automatically configure the user tag for the user identifier based on the user behavior data, so that when data pushing is carried out, a data receiving party does not need to be manually selected, the data receiving party can be quickly determined based on the target user tag, and the data pushing efficiency is improved. When data pushing is carried out, a data pushing task is established uniformly by the management terminal, after the data pushing task is received by the transfer terminal, data to be pushed can be sent to the target user terminal by one key only through simple confirmation operation, manual selection of the data to be pushed and a data receiving party by the transfer terminal is not needed, and the data pushing efficiency is further improved.

In one embodiment, the manner of obtaining the user behavior data includes at least one of the following manners, including:

and pulling a session record of the current user identifier and the associated application session object from a second server corresponding to the associated application of the target application, extracting a session message of which the message sender is the current user identifier from the session record as an initial session message, and obtaining user behavior data corresponding to the current user identifier based on the initial session message.

Specifically, the second server refers to an application server corresponding to the associated application, and therefore, session records of each cluster user in the user cluster are stored on the second server. The first server is an application server corresponding to the management application, and the management application serves the associated application, so that the first server can obtain the session record of the cluster user from the second server. The first server may specifically invoke a related interface provided by the second server, periodically pull the session record of the current user identifier and the associated application session object from the second server, then extract the session message of the message sender as the current user identifier from the session record as the initial session message, and use the initial session message as the user behavior data corresponding to the current user identifier. That is, the first server periodically pulls the session record generated in the chat process between the individual user and the cluster user from the second server, extracts the session message sent by the individual user from the session record as the initial session message, and uses the initial session message as the user behavior data corresponding to the individual user.

In one embodiment, in order to improve the reasonableness, the legality and the safety of the stored session record, the second server stores the session message generated by the individual user and the cluster user in the chat process as the session record after the individual user and the cluster user both agree with the authorization of session archiving. Further, for the cluster users, an administrator may uniformly set which cluster users need to perform session archiving, or the cluster users themselves set authorization to agree with the session archiving in the associated application. For the individual user, session archiving authorization inquiry information can be sent in a session interface between the cluster user and the individual user to inquire whether the individual user agrees to perform session archiving.

Receiving a group entry behavior message sent by the second server through the callback interface, and obtaining user behavior data corresponding to the current user identifier based on the group entry behavior message; the group entering behavior message carries the session identifier of the session group to which the current user identifier is added.

Specifically, the first server may also receive an entering-group behavior message corresponding to the current user identifier, which is sent by the second server through the callback interface in real time, and use the entering-group behavior message as user behavior data corresponding to the current user identifier. The group entry behavior message carries the session identifier of the session group to which the current user identifier is added, and is used for describing which session group the current individual user is added to. The second server records the updating condition of the session members of each session group in the user cluster communication application in real time, for example, the addition and reduction of the session members, the change of the session administrator, and the like.

Acquiring buried point data reported by a current user terminal corresponding to a current user identifier, and acquiring user behavior data corresponding to the current user identifier based on the buried point data; the buried point data is obtained by detecting the interaction action of the current user identification on the push data.

Specifically, the embedding can be performed at a client of the target application, and when an individual user generates an interactive behavior, user behavior data is recorded to obtain the embedding data. The first server can obtain the data of the buried point reported by the current user terminal corresponding to the current user identifier, and the data of the buried point is used as the user behavior data corresponding to the current user identifier. The buried point data is obtained by detecting the interaction behavior of the current user identification acting on the push data, for example, the buried point data records the click events of the individual users for various push data.

In the embodiment, different types of user behavior data are acquired through different channels, and the user behavior data can be enriched, so that more accurate user tags can be configured for individual users from multiple angles, and the accuracy and the effectiveness of data pushing are improved.

In one embodiment, obtaining user behavior data corresponding to the current user identifier based on the group entry behavior message includes:

and acquiring the group entering mode corresponding to the group entering behavior message from the second server, and acquiring user behavior data corresponding to the current user identifier based on the group entering behavior message and the group entering mode.

Specifically, if the group entry behavior tag needs to be determined in consideration of the group entry mode, the first server may further call a related interface of the second server, and obtain the group entry mode corresponding to the group entry behavior message from the second server, so as to obtain the user behavior data corresponding to the current user identifier based on the group entry behavior message and the group entry mode.

In one embodiment, determining the user label corresponding to each user identifier based on the user behavior data includes:

extracting target behavior data from the user behavior data based on the strategy reference information corresponding to the label matching strategy; storing the target behavior data into a message queue; and reading the target behavior data from the message queue, and performing label matching processing on the target behavior data based on a label matching strategy to obtain user labels corresponding to the user identifications.

The strategy reference information is used for preprocessing the user behavior data, filtering useless and redundant information from the user behavior data, and extracting effective target behavior data. It is to be understood that different types of tag matching policies may correspond to different policy reference information. The policy reference information may be at least one to-be-matched data corresponding to a candidate tag in the tag matching policy, for example, a candidate session identifier in the grouping behavior matching policy.

The message queue is a container for storing messages and data during data transmission. The message queue can ensure stable delivery of the message, e.g., if the recipient fails when sending the message, the message queue will also hold the message until it can be successfully delivered.

Specifically, the first server may extract target behavior data from the user behavior data based on policy reference information corresponding to the tag matching policy, and filter redundant information, thereby reducing processing pressure of subsequent tag matching processing. Since the target behavior data needs to be analyzed item by item for subsequent tag matching processing, in order to ensure the stability of data processing, the first server may store the target behavior data item by item into the message queue. When performing tag matching, the first server may read target behavior data from the message queue one by one, perform tag matching processing on the target behavior data based on a pre-configured tag matching policy, and finally obtain user tags corresponding to each user identifier based on a processing result.

In one embodiment, the first server can perform division work cooperation in the system, and different service modules are responsible for different data processing works, so that the data processing efficiency is improved. For example, the data synchronization service module may obtain the user behavior data from the second server, extract the target behavior data from the user behavior data based on the policy reference information corresponding to the tag matching policy, and store the target behavior data in the message queue. And the tag service module reads the target behavior data from the message queue, performs tag matching processing on the target behavior data based on a tag matching strategy to obtain user tags corresponding to the user identifications, and stores the user identifications and the corresponding user tags, so that subsequent checking and use are facilitated.

In the above embodiment, the target behavior data is extracted from the user behavior data based on the policy reference information corresponding to the tag matching policy, so that the calculation amount of subsequent data processing can be reduced. The target behavior data are stored through the message queue, and the stability of data processing can be guaranteed. And performing label matching processing on the target behavior data based on the label matching strategy, so that the user label corresponding to each user identification can be rapidly and intelligently determined.

In one embodiment, the target behavior data includes different types of target behavior data, and each type has a corresponding message queue and tag matching policy.

Storing the target behavior data into a message queue, comprising: and storing the same type of target behavior data into the corresponding message queue.

Reading target behavior data from the message queue, and performing tag matching processing on the target behavior data based on a tag matching strategy to obtain user tags corresponding to user identifications, wherein the tag matching processing method comprises the following steps: and reading corresponding target behavior data from the message queue of the current type, and performing label matching processing on the corresponding target behavior data based on a label matching strategy corresponding to the current type to obtain user labels of the user identifications corresponding to the current type.

Specifically, in order to further improve the data processing efficiency, different types of target behavior data may be stored in corresponding types of message queues, and the different types of target behavior data may be subjected to tag matching processing by using a corresponding type of tag matching policy. Therefore, the first server may store the same type of target behavior data in the corresponding message queue, for example, store the target behavior data of the session message type in the message queue corresponding to the session message type. Similarly, the first server may read corresponding target behavior data from the message queue of the specific type, and perform tag matching processing on the corresponding target behavior data based on the tag matching policy corresponding to the type, thereby obtaining a user tag corresponding to each user identifier in the type. For example, target behavior data of the session message type is read from a message queue corresponding to the session message type, and tag matching processing is performed on the target behavior data of the session message type based on a keyword matching policy, so as to obtain a user tag, namely a keyword tag, of the session message type corresponding to the individual user.

In the above embodiment, different types of target behavior data are stored in the message queues of corresponding types, and the different types of target behavior data are subjected to tag matching processing by using tag matching policies of corresponding types, so that data processing efficiency can be improved, and user tags corresponding to user identifiers can be determined quickly.

In one embodiment, extracting target behavior data from user behavior data based on policy reference information corresponding to a tag matching policy includes:

when the tag matching strategy is a keyword matching strategy, taking a target transit user identification in the keyword matching strategy as corresponding strategy reference information, acquiring an intermediate conversation message from user behavior data corresponding to the current user identification as a reference conversation message, and taking the reference conversation message as target behavior data corresponding to the current user identification; and the message receiver and the message sender corresponding to the intermediate session message are respectively a target transfer user identifier and a current user identifier.

The message receiver and the message sender corresponding to the intermediate session message are respectively a target relay user identifier and a current user identifier, that is, the intermediate session message is a session message sent by a current individual user to a target cluster user in a chat process between the current individual user and the target cluster user.

Specifically, for the keyword matching policy, the target relay user identifier in the keyword matching policy may be used as the policy reference information corresponding to the keyword matching policy. Then, the first server may obtain, from the user behavior data corresponding to the current user identifier, a session message between the current individual user and the target cluster user as a reference session message, filter the session message between the current individual user and other cluster users, and further use the reference session message as the target behavior data corresponding to the current user identifier.

In an embodiment, the reference session type in the keyword matching policy may be further used as corresponding policy reference information, and then, the first server may obtain, from the user behavior data corresponding to the current user identifier, an intermediate session message whose session type is the reference session type, as the reference session message. For example, the reference session type is a single-person session type, and a single-person session message sent by the current individual user to the target cluster user may be used as the reference session message.

And when the tag matching strategy is the grouping behavior matching strategy, taking the candidate session identification in the grouping behavior matching strategy as corresponding strategy reference information, acquiring grouping behavior information and a grouping mode corresponding to the candidate session identification from the user behavior data corresponding to the current user identification as target grouping behaviors, and taking the target grouping behaviors as target behavior data corresponding to the current user identification.

Specifically, for the matching policy of the grouping behavior, the candidate session identifier in the matching policy of the grouping behavior may be used as the policy reference information corresponding to the matching policy of the grouping behavior. Then, the first server may obtain, from the user behavior data corresponding to the current user identifier, the group entry behavior message and the group entry manner corresponding to the candidate session identifier as a target group entry behavior, filter the group entry behavior message and the group entry manner corresponding to other session identifiers, and further take the target group entry behavior as target behavior data corresponding to the current user identifier.

When the tag matching strategy is the interaction behavior matching strategy, the candidate push data in the interaction behavior matching strategy is used as corresponding strategy reference information, buried point data corresponding to the candidate push data is obtained from the user behavior data corresponding to the current user identification to be used as a target interaction behavior, and the target interaction behavior is used as target behavior data corresponding to the current user identification.

Specifically, for the interaction behavior matching policy, candidate pushed data in the interaction behavior matching policy may be used as policy reference information corresponding to the group entry behavior matching policy. Then, the first server may obtain buried point data corresponding to the candidate push data from the user behavior data corresponding to the current user identifier as a target interaction behavior, filter the buried point data corresponding to other push data, and use the target interaction behavior as target behavior data corresponding to the current user identifier.

In the above embodiment, different tag matching strategies correspond to different strategy reference information, so that the user behavior data can be preprocessed in a targeted manner, and the target behavior data can be obtained quickly.

In one embodiment, performing tag matching processing on target behavior data based on a tag matching policy to obtain a user tag corresponding to each user identifier includes:

and when the label matching strategy is a keyword matching strategy, matching the reference session message with each candidate keyword, and taking the candidate label corresponding to the candidate keyword which is successfully matched as the user label corresponding to the current user identifier.

Specifically, if the tag matching policy is a keyword matching policy, when performing tag matching processing, the first server may match the reference session message read from the message queue with each candidate keyword, and use a candidate tag corresponding to a candidate keyword that is successfully matched as a user tag corresponding to the current user identifier.

When the tag matching strategy is the grouping behavior matching strategy, matching the grouping mode corresponding to the target grouping behavior with each intermediate grouping mode, and taking the candidate tag corresponding to the successfully matched intermediate grouping mode as the user tag corresponding to the current user identifier; and the session identification corresponding to the target group entering behavior is consistent with the candidate session identification corresponding to the intermediate group entering mode.

Specifically, if the tag matching policy is the grouping behavior matching policy, when performing tag matching processing, the first server may match the grouping manner corresponding to the target grouping behavior read from the message queue with each intermediate grouping manner corresponding to the same session identifier, and use a candidate tag corresponding to the intermediate grouping manner that is successfully matched as the user tag corresponding to the current user identifier.

When the tag matching strategy is an interactive behavior matching strategy, matching interactive behavior information corresponding to the target interactive behavior with each piece of intermediate interactive behavior information, and taking a candidate tag corresponding to the successfully matched intermediate interactive behavior information as a user tag corresponding to the current user identifier; and the candidate push data corresponding to the intermediate interaction behavior information is consistent with the push data corresponding to the target interaction behavior.

Specifically, if the tag matching policy is an interaction behavior matching policy, when performing tag matching processing, the first server may match interaction behavior information corresponding to the target interaction behavior read from the message queue with each piece of intermediate interaction behavior information corresponding to the same push data, and use a candidate tag corresponding to the successfully matched intermediate interaction behavior information as a user tag corresponding to the current user identifier.

In the above embodiment, the target behavior data is subjected to tag matching processing based on the specific content of the tag matching policy, so that an accurate user tag corresponding to each user identifier can be obtained.

In a specific embodiment, the data pushing method comprises the following steps:

1. the method comprises the steps that an administrator terminal configures a label matching strategy in enterprise management application, and sends the label matching strategy to an application server (namely a first server) corresponding to the enterprise management application.

The enterprise management application serves enterprise communication applications, and the enterprise communication applications and the individual communication applications are in an association relation.

2. The enterprise member terminals communicate information with the external contacts (namely clients) of the enterprise through the enterprise communication application and the individual communication application, so that user behavior data corresponding to the external contacts of the enterprise are generated.

3. The first server obtains user behavior data corresponding to each enterprise external contact person, and configures corresponding user tags for each enterprise external contact person based on the user behavior data.

3-1, extracting target behavior data from the user behavior data by the first server based on the strategy reference information corresponding to the label matching strategy.

3-2, the first server stores the target behavior data into a message queue.

And 3-3, the first server reads the target behavior data from the message queue, and performs label matching processing on the target behavior data based on a label matching strategy to obtain user labels corresponding to the external contacts of each enterprise.

4. The first server forms a candidate label set based on user labels corresponding to the contacts outside the enterprise, and sends the candidate label set to the administrator terminal.

5. The administrator terminal displays the candidate label set on the pushing task configuration interface, responds to configuration operation triggered on the pushing task configuration interface, and displays pushing configuration information, wherein the pushing configuration information comprises data to be pushed and a target user label, and the target user label is determined from the candidate label set. And the administrator terminal responds to the confirmation operation aiming at the push configuration information, generates a data push task based on the push configuration information, and sends the data push task to the transfer terminal.

6. And the enterprise member terminal responds to the confirmation operation aiming at the data pushing task and pushes the data to be pushed to the enterprise external contact terminal corresponding to the target user label.

Referring to fig. 10A, an administrator of an enterprise may configure a keyword matching policy (which may also be referred to as a customer keyword tagging rule) in an enterprise management application of an administrator terminal. After the enterprise members and the clients agree to the communication application session archiving authorization, the first server marks user tags for the clients which refer to the specified keywords in the communication application chat process.

During the chat process between the enterprise members and the clients, the application server (i.e., the second server) corresponding to the enterprise communication application archives the session messages, and the data synchronization service in the first server pulls the session archive records from the second server at regular time according to a certain frequency. After the data synchronization service pulls the session record, the session content is analyzed to obtain a single session message, and then the session messages are sent to the message queue one by one according to the message dimension. And the label service in the first server subscribes the session message in the message queue and performs label matching processing on the message content of the session message according to a preset keyword matching strategy. And if the session message hits the corresponding label rule, configuring a corresponding user label for the client, and persistently storing the client and the corresponding user label data so as to facilitate subsequent retrieval and use.

Referring to fig. 10B, an administrator of an enterprise may configure a grouping behavior matching policy (which may also be referred to as a customer grouping behavior tagging rule) in an enterprise management application of an administrator terminal. When a client joins a designated session group, the first server will automatically tag the clustered client with a user label.

After the client agrees to join the session group, the second server synchronizes the group entry message to the data synchronization service of the first server through the callback interface, that is, the first server receives the group member callback event sent by the second server. And after receiving the callback data, the data synchronization service preprocesses the group entering message, preprocesses the group entering message according to the session identifier in the preset group entering behavior matching strategy, and filters the group entering message of the non-specific session group. After receiving the callback data, the data synchronization service can also call the enterprise communication application related interface to acquire the group entering mode corresponding to the group entering message, so as to supplement the group entering mode. The data synchronization service sends the group-entry message and the corresponding group-entry mode to the message queue. And the tag service subscribes the group entering information in the information queue, performs tag matching processing on the information content of the group entering information according to a pre-configured group entering behavior matching strategy, configures a corresponding user tag for the client if the group entering information hits a corresponding tag rule, and performs persistent storage on the client and corresponding user tag data, so as to facilitate subsequent retrieval and use.

Referring to fig. 10C, an administrator of the enterprise may configure an interactive behavior matching policy (which may also be referred to as a customer material interactive tagging rule) in an enterprise management application at an administrator terminal. When a client browses a specific material sent by an enterprise member and the browsing behavior meets a certain condition, the first server automatically marks a user tag for the client. For example, when the browsing time and the browsing times meet the policy requirements, the user tag is automatically marked on the client.

In the process of browsing materials, a client terminal reports corresponding buried point data to the buried point service of the first server, wherein the buried point data comprises user information, material information, behavior information and other data. After receiving the buried point data, the buried point service can preprocess the buried point data according to the candidate push data in the interactive behavior matching strategy, filter the buried point data corresponding to the non-specific material, and send the buried point data to the message queue. And the stream processing service of the first server subscribes the buried point data in the message queue, and performs label matching processing on the buried point data according to an interactive behavior matching strategy, wherein the matching is mainly performed from the aspects of interactive frequency, times, time dimension and the like. And if the buried point data hits the corresponding label rule, configuring a corresponding user label for the client, and persistently storing the client and the corresponding user label data so as to facilitate subsequent retrieval and use. The stream processing service refers to a stream data aggregation and calculation service.

In one embodiment, for session messages and group entry information, the Message queue may employ tdmq (tencent Distributed Message queue) of the Tencent cloud. For buried point data, the message queue may use ckafka (cloud kafka) of Tencent cloud. Further, session messages and group information may be stored in different message queues. The stream processing service may be Oceanus (structured based on Apache Flink, streaming data aggregation and computation service located in the cloud) of Tencent cloud. The data persistence storage can adopt an Elastic Search (a Search server based on Lucene) of Tencent cloud, and writes the user identification of the client and the corresponding user tag into a document of the Elastic Search for persistence storage.

In the embodiment, the automation of the label printing process for the client can be realized only by performing simple label matching strategy configuration operation on the client of the enterprise management application by enterprise members, and the problems of tedious manual label printing process, low efficiency and inadequately objective label printing in the traditional technology are solved. The enterprise can also carry out accurate grouping operation on the clients better subsequently, and the operation efficiency for the clients is greatly improved. Moreover, enterprise members can realize the automation of data pushing for clients only by performing simple data pushing configuration operation on the client of the enterprise management application and performing simple confirmation operation on the client of the enterprise communication application, and the problems of complicated flow and low efficiency of manual data pushing in the traditional technology are solved.

In one embodiment, as shown in fig. 11, a data push system is provided, which includes a first server 1102, a management terminal 1104, a transit terminal 1106 and a target user terminal 1108.

The first server 1102 is configured to configure corresponding user tags for each user identifier based on user behavior data in the target application, form a candidate tag set, and send the candidate tag set to the management terminal.

The management terminal 1104 is configured to display the candidate tag set on the push task configuration interface, determine a target user tag from the candidate tag set, generate push configuration information based on the data to be pushed and the target user tag, generate a data push task based on the push configuration information, and send the data push task to the relay terminal.

The transit terminal 1106 is configured to, in response to a confirmation operation for the data pushing task, push the data to be pushed to the target user terminal 1008 corresponding to the target user tag.

It is to be understood that the specific data processing procedures of the first server, the management terminal and the transit terminal may refer to the methods described in the foregoing respective related embodiments.

In the data pushing system, the management terminal establishes the data pushing task in a unified mode, the transfer terminal can send data to be pushed to the target user terminal in a one-key mode only by simple confirmation operation after receiving the data pushing task, manual selection of the data to be pushed and a data receiving party by the transfer terminal is not needed, and data pushing efficiency is improved. In addition, the first server can automatically configure the user tag for the user identifier based on the user behavior data, so that when data pushing is carried out, a data receiving party does not need to be manually selected, the data receiving party can be quickly determined based on the target user tag, and the data pushing efficiency is further improved.

In one embodiment, as shown in FIG. 12, the data push system further comprises a second server 1010. The first server can obtain the conversation message and the group-entering behavior message of the individual user from the second server as the user behavior data. The second server can acquire data from the transit terminal to obtain information such as session messages and group entry behavior messages of the cluster users and the individual users.

It should be understood that although the steps in the flowcharts of fig. 2, 6, and 9 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2, 6, and 9 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least some of the other steps or stages.

In one embodiment, as shown in fig. 13, there is provided a data pushing apparatus 1300, which may be a part of a computer device using a software module or a hardware module, or a combination of the two, the apparatus specifically includes: a push information configuration module 1302 and a push task generation module 1304, wherein:

a push information configuration module 1302, configured to respond to a configuration operation of data push, and display push configuration information; the push configuration information comprises data to be pushed and target user tags, wherein the user tags are tags configured for user identifications by the first server based on user behavior data in the target application;

a push task generating module 1304, configured to generate a data push task based on the push configuration information in response to the confirmation operation for the push configuration information, and send the data push task to the relay terminal, so that the relay terminal pushes the data to be pushed to the target user terminal corresponding to the target user tag in response to the confirmation operation for the data push task.

According to the data pushing device, the management terminal establishes the data pushing task in a unified mode, the transfer terminal can send the data to be pushed to the target user terminal in a one-key mode only through simple confirmation operation after receiving the data pushing task, manual selection of the data to be pushed and a data receiving party by the transfer terminal is not needed, and data pushing efficiency is improved. In addition, the first server can automatically configure the user tag for the user identifier based on the user behavior data, so that when data pushing is carried out, a data receiving party does not need to be manually selected, the data receiving party can be quickly determined based on the target user tag, and the data pushing efficiency is further improved.

In one embodiment, the data pushing apparatus 1300 further comprises:

the policy configuration module is used for responding to the starting operation of the management application, displaying a policy configuration interface, and enabling the management application to serve the associated application corresponding to the target application; determining a tag matching strategy in response to configuration operation triggered on a strategy configuration interface; the label matching strategy is used for carrying out label matching processing on the user behavior data corresponding to the current user identification and determining the user label corresponding to the current user identification.

In one embodiment, the policy configuration module includes:

the keyword matching strategy configuration unit is used for responding to the configuration operation of the keyword label in a keyword label configuration area of a strategy configuration interface and displaying keyword label configuration information; the keyword tag configuration information comprises candidate tags and corresponding candidate keywords; responding to the confirmation operation aiming at the keyword tag configuration information, and generating a keyword matching strategy based on the keyword tag configuration information to obtain a tag matching strategy; the keyword matching strategy is used for determining that the user label corresponding to the current user identifier is a candidate label corresponding to the candidate keyword which is successfully matched when at least one historical conversation message in the user behavior data corresponding to the current user identifier is successfully matched with the candidate keyword.

In one embodiment, the keyword tag configuration information further includes at least one of a reference keyword matching pattern and a reference transit user identifier corresponding to the candidate tag. The keyword matching strategy configuration unit is also used for responding to the configuration operation of the keyword matching mode and determining a reference keyword matching mode from the candidate keyword matching modes; the candidate keyword matching mode comprises a coarse-grained matching mode and a fine-grained matching mode, the coarse-grained matching mode is used for determining that the historical conversation message and the candidate keyword are successfully matched when the historical conversation message comprises the candidate keyword, and the fine-grained matching mode is used for determining that the historical conversation message and the candidate keyword are successfully matched when the historical conversation message is the candidate keyword.

The keyword matching strategy configuration unit is also used for responding to the configuration operation of the transit user identification and determining a reference transit user identification from the candidate transit user identifications; the reference relay user identifier is used for determining that the user tag corresponding to the current user identifier is the candidate tag corresponding to the candidate keyword which is successfully matched when the historical conversation message is successfully matched with the candidate keyword and the conversation user identifier corresponding to the historical conversation message comprises the target relay user identifier corresponding to the candidate keyword which is successfully matched.

In one embodiment, the policy configuration module includes:

the system comprises a grouping behavior matching strategy configuration unit, a grouping behavior matching strategy configuration unit and a grouping behavior matching strategy configuration unit, wherein the grouping behavior matching strategy configuration unit is used for responding to the configuration operation of a grouping behavior tag in a grouping behavior tag configuration area of a strategy configuration interface and displaying grouping behavior tag configuration information; the configuration information of the clustering behavior tags comprises candidate tags and corresponding candidate session identifications; responding to the confirmation operation aiming at the configuration information of the group entry behavior tags, and generating a group entry behavior matching strategy based on the configuration information of the group entry behavior tags to obtain a tag matching strategy; the matching strategy of the group-entering behavior is used for determining that the user label corresponding to the current user identification is the candidate label corresponding to the candidate session identification which is successfully matched when the target session identification is successfully matched with the candidate session identification, and the target session identification is the session identification corresponding to the target group-entering behavior in the user behavior data corresponding to the current user identification.

In one embodiment, the grouping behavior tag configuration information further includes a reference grouping manner corresponding to the candidate tag. The group entry behavior matching strategy configuration unit is also used for responding to the configuration operation of the group entry mode and determining the reference group entry mode; and the reference group entering mode is used for determining that the user label corresponding to the current user identification is the corresponding candidate label when the group entering mode corresponding to the target group entering behavior is also successfully matched with the reference group entering mode corresponding to the successfully matched candidate session identification.

In one embodiment, the data pushing apparatus 1300 further comprises:

the data uploading module is used for displaying a data uploading interface; and uploading a plurality of candidate push data in a data uploading interface.

The policy configuration module includes:

the interactive behavior matching strategy configuration unit is used for responding to the configuration operation of the interactive behavior label in an interactive behavior label configuration area of the strategy configuration interface and displaying the configuration information of the interactive behavior label; the interaction behavior tag configuration information comprises candidate tags, corresponding candidate push data and candidate interaction behavior information; responding to the confirmation operation aiming at the interactive behavior tag configuration information, and generating an interactive behavior matching strategy based on the interactive behavior tag configuration information to obtain a tag matching strategy; the interaction behavior matching strategy is used for determining that the user tag corresponding to the current user identifier is the candidate tag corresponding to the candidate push data which is successfully matched when the push data corresponding to the target interaction behavior is successfully matched with the candidate push data and the interaction behavior information corresponding to the target interaction behavior is also successfully matched with the candidate interaction behavior information corresponding to the candidate push data which is successfully matched, and the target interaction behavior is acquired from the user behavior data corresponding to the current user identifier.

In one embodiment, the push information configuration module is further configured to display a push task configuration interface; determining data to be pushed in response to a push data selection operation triggered on a push task configuration interface; and determining a target user tag in response to a user tag selection operation triggered on the push task configuration interface.

In one embodiment, the push configuration information further includes at least one of a target push manner and a target transit user identifier. The push information configuration module is also used for responding to the transit user identifier selection operation triggered on the push task configuration interface and determining a target transit user identifier; the transfer terminal is a user terminal corresponding to the target transfer user identifier; and determining a target pushing mode in response to a pushing mode selection operation triggered on the pushing task configuration interface.

In one embodiment, as shown in fig. 14, a data pushing apparatus 1400 is provided, which may be a part of a computer device using a software module or a hardware module, or a combination of the two modules, and specifically includes: a push task display module 1402 and a push task execution module 1404, wherein:

a push task display module 1402, configured to display a data push task sent by the management terminal; the data pushing task is generated by the management terminal based on pushing configuration information in response to a confirmation operation aiming at the pushing configuration information, the pushing configuration information is obtained by the management terminal in response to a configuration operation of data pushing, and the pushing configuration information comprises data to be pushed and a target user label; the user label is a label configured for each user identifier by the first server based on user behavior data in the target application;

the push task executing module 1404 is configured to, in response to a confirmation operation for the data push task, push data to be pushed to a target user terminal corresponding to a target user tag.

In one embodiment, the push task display module is further configured to display a session management interface in response to a start operation of an associated application corresponding to the target application; the session management interface displays a session entrance of a management session interface with the transit terminal and the management terminal; responding to a trigger operation aiming at a session entrance, and entering a management session interface; and displaying the data pushing task in the management session interface.

In one embodiment, the data pushing device 1400 further comprises:

the session sharing module is used for responding to session sharing operation aiming at the data to be pushed and displaying a session sharing configuration interface; the session sharing configuration interface comprises a user tag configuration area; displaying a target user tag in response to a configuration operation for the user tag configuration area; and responding to the sharing confirmation operation aiming at the data to be pushed, sending the data to be pushed as a target session message to a target session interface, wherein the target session interface is a session interface of the transfer terminal and the target user terminal in the associated application corresponding to the target application.

In one embodiment, the data pushing device 1400 further comprises:

the dynamic information sharing module is used for responding to dynamic information sharing operation aiming at the data to be pushed and displaying a dynamic information sharing configuration interface; the dynamic information sharing configuration interface comprises a user tag configuration area; displaying a target user tag in response to a configuration operation for the user tag configuration area; and responding to the sharing confirmation operation aiming at the data to be pushed, sending the data to be pushed as target dynamic information to the target user terminal, and displaying the target dynamic information on a dynamic information display interface of the target application at the target user terminal.

In one embodiment, the data pushing device 1400 further comprises:

the conversation creating module is used for displaying a conversation creating interface; the session creation interface comprises a user tag configuration area; determining a target user tag in response to a configuration operation for the user tag configuration area; responding to the creation operation of the session group, establishing a target session group corresponding to the target user label, generating group-entering invitation information corresponding to the target session group, and sending the group-entering invitation information to a target session interface, wherein the target session interface is a session interface of the relay terminal and the target user terminal in an associated application corresponding to the target application.

In one embodiment, the data pushing device 1400 further comprises:

the behavior track display module is used for displaying the behavior track data corresponding to the current user identifier in a user information display interface corresponding to the current user identifier; the behavior trace data is trace data obtained by performing behavior arrangement on user behavior data corresponding to the current user identifier.

In one embodiment, as shown in fig. 15, there is provided a tag processing apparatus, which may be a part of a computer device using a software module or a hardware module, or a combination of the two, and specifically includes: a user data acquisition module 1502, a user tag determination module 1504, and a user tag transmission module 1608, wherein:

a user data obtaining module 1502, configured to obtain user behavior data corresponding to each user identifier in a target application;

a user tag determining module 1504, configured to determine, based on the user behavior data, user tags corresponding to the user identifiers to form a candidate tag set;

the user tag sending module 1508, configured to send the candidate tag set to the management terminal, so that the management terminal displays the candidate tag set on the push task configuration interface, and determines a target user tag from the candidate tag set; the target user tag is used for data pushing, a data pushing process is that the management terminal sends a data pushing task to the transfer terminal so that the transfer terminal responds to a confirmation operation for the data pushing task and pushes data to be pushed to the target user terminal corresponding to the target user tag, the data pushing task is generated based on pushing configuration information, and the pushing configuration information comprises the data to be pushed and the target user tag.

According to the label processing device, the first server can automatically configure the user label for the user identifier based on the user behavior data, so that when data pushing is carried out, a data receiving party does not need to be manually selected, the data receiving party can be rapidly determined based on the target user label, and the data pushing efficiency is improved. When data pushing is carried out, a data pushing task is established uniformly by the management terminal, after the data pushing task is received by the transfer terminal, data to be pushed can be sent to the target user terminal by one key only through simple confirmation operation, manual selection of the data to be pushed and a data receiving party by the transfer terminal is not needed, and data pushing efficiency is improved.

In an embodiment, the user data obtaining module is further configured to pull a session record of the current user identifier and the associated application session object from a second server corresponding to the associated application of the target application, extract a session message of which the message sender is the current user identifier from the session record as an initial session message, and obtain user behavior data corresponding to the current user identifier based on the initial session message.

The user data acquisition module is also used for receiving the group entry behavior message sent by the second server through the callback interface and acquiring user behavior data corresponding to the current user identifier based on the group entry behavior message; the group entering behavior message carries the session identifier of the session group to which the current user identifier is added.

The user data acquisition module is also used for acquiring buried point data reported by the current user terminal corresponding to the current user identifier and acquiring user behavior data corresponding to the current user identifier based on the buried point data; the buried point data is obtained by detecting the interaction action of the current user identification on the push data.

In an embodiment, the user data obtaining module is further configured to obtain, from the second server, an entry manner corresponding to the entry behavior message, and obtain, based on the entry behavior message and the entry manner, user behavior data corresponding to the current user identifier.

In one embodiment, the user tag determination module comprises:

the target behavior data determining unit is used for extracting target behavior data from the user behavior data based on the strategy reference information corresponding to the label matching strategy;

the target behavior data storage unit is used for storing the target behavior data into the message queue;

and the target behavior data processing unit is used for reading the target behavior data from the message queue and carrying out label matching processing on the target behavior data based on a label matching strategy to obtain user labels corresponding to the user identifications.

In one embodiment, the target behavior data includes different types of target behavior data, and each type has a corresponding message queue and tag matching policy. The target behavior data storage unit is also used for storing the same type of target behavior data into the corresponding message queue. The target behavior data processing unit is further configured to read corresponding target behavior data from the message queue of the current type, and perform tag matching processing on the corresponding target behavior data based on a tag matching policy corresponding to the current type, so as to obtain a user tag corresponding to each user identifier in the current type.

In one embodiment, the target behavior data determining unit is further configured to, when the tag matching policy is a keyword matching policy, use a target transit user identifier in the keyword matching policy as corresponding policy reference information, obtain an intermediate session message from user behavior data corresponding to a current user identifier as a reference session message, and use the reference session message as target behavior data corresponding to the current user identifier; and the message receiver and the message sender corresponding to the intermediate session message are respectively a target transfer user identifier and a current user identifier.

The target behavior data determining unit is further configured to, when the tag matching policy is the grouping behavior matching policy, use the candidate session identifier in the grouping behavior matching policy as corresponding policy reference information, obtain, from the user behavior data corresponding to the current user identifier, a grouping behavior message and a grouping manner corresponding to the candidate session identifier as a target grouping behavior, and use the target grouping behavior as target behavior data corresponding to the current user identifier.

The target behavior data determining unit is further configured to, when the tag matching policy is the interaction behavior matching policy, use the candidate push data in the interaction behavior matching policy as corresponding policy reference information, obtain buried point data corresponding to the candidate push data from the user behavior data corresponding to the current user identifier as a target interaction behavior, and use the target interaction behavior as target behavior data corresponding to the current user identifier.

In an embodiment, the target behavior data processing unit is further configured to, when the tag matching policy is a keyword matching policy, match the reference session message with each candidate keyword, and use a candidate tag corresponding to a candidate keyword that is successfully matched as a user tag corresponding to the current user identifier.

The target behavior data processing unit is further used for matching the grouping mode corresponding to the target grouping behavior with each intermediate grouping mode when the tag matching strategy is the grouping behavior matching strategy, and taking the candidate tag corresponding to the successfully matched intermediate grouping mode as the user tag corresponding to the current user identifier; and the session identification corresponding to the target group entering behavior is consistent with the candidate session identification corresponding to the intermediate group entering mode.

The target behavior data processing unit is further used for matching interaction behavior information corresponding to the target interaction behavior with each piece of intermediate interaction behavior information when the tag matching strategy is an interaction behavior matching strategy, and taking a candidate tag corresponding to the successfully matched intermediate interaction behavior information as a user tag corresponding to the current user identifier; and the candidate push data corresponding to the intermediate interaction behavior information is consistent with the push data corresponding to the target interaction behavior.

For specific limitations of the data pushing device and the tag processing device, reference may be made to the above limitations of the data pushing method and the tag processing method, which are not described herein again. The modules in the data pushing device and the label processing device can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 16. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing data such as user tags, tag matching strategies and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a tag processing method.

In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 17. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a data push method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by those skilled in the art that the configurations shown in fig. 16 and 17 are block diagrams of only some of the configurations relevant to the present disclosure, and do not constitute a limitation on the computing devices to which the present disclosure may be applied, and that a particular computing device may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.

In an embodiment, a computer-readable storage medium is provided, in which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.

In one embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer-readable storage medium. The computer instructions are read by a processor of a computer device from a computer-readable storage medium, and the computer instructions are executed by the processor to cause the computer device to perform the steps in the above-mentioned method embodiments.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A data pushing method is applied to a management terminal, and comprises the following steps:

2. The method of claim 1, wherein prior to the configuration operation in response to the data push, the method further comprises:

responding to the starting operation of a management application, and displaying a policy configuration interface, wherein the management application serves the associated application corresponding to the target application;

responding to configuration operation triggered on the strategy configuration interface, and determining a label matching strategy; and the label matching strategy is used for carrying out label matching processing on the user behavior data corresponding to the current user identification and determining the user label corresponding to the current user identification.

3. The method of claim 2, wherein determining that a tag matches a policy in response to a configuration operation triggered at the policy configuration interface comprises:

in a keyword tag configuration area of the strategy configuration interface, responding to the configuration operation of a keyword tag, and displaying keyword tag configuration information; the keyword tag configuration information comprises candidate tags and corresponding candidate keywords;

responding to the confirmation operation aiming at the keyword label configuration information, generating a keyword matching strategy based on the keyword label configuration information, and obtaining the label matching strategy; and the keyword matching strategy is used for determining that the user label corresponding to the current user identifier is a candidate label corresponding to the candidate keyword which is successfully matched when at least one historical conversation message in the user behavior data corresponding to the current user identifier is successfully matched with the candidate keyword.

4. The method according to claim 3, wherein the keyword tag configuration information further includes at least one of a reference keyword matching pattern and a reference transit user identifier corresponding to the candidate tag;

the displaying, in the keyword tag configuration area of the policy configuration interface, the keyword tag configuration information in response to the configuration operation of the keyword tag includes:

determining the reference keyword matching pattern from candidate keyword matching patterns in response to a configuration operation of the keyword matching patterns; the candidate keyword matching pattern comprises a coarse-grained matching pattern and a fine-grained matching pattern, the coarse-grained matching pattern is used for determining that the historical conversation message is successfully matched with the candidate keyword when the historical conversation message comprises the candidate keyword, and the fine-grained matching pattern is used for determining that the historical conversation message is successfully matched with the candidate keyword when the historical conversation message is the candidate keyword;

responding to configuration operation of the transit user identification, and determining the reference transit user identification from candidate transit user identifications; and the reference relay user identifier is used for determining that the user label corresponding to the current user identifier is the candidate label corresponding to the candidate keyword which is successfully matched when the historical conversation message is successfully matched with the candidate keyword and the conversation user identifier corresponding to the historical conversation message comprises the target relay user identifier corresponding to the candidate keyword which is successfully matched.

5. The method of claim 2, wherein determining that a tag matches a policy in response to a configuration operation triggered at the policy configuration interface comprises:

in a group entry behavior tag configuration area of the strategy configuration interface, responding to configuration operation of a group entry behavior tag, and displaying group entry behavior tag configuration information; the configuration information of the group entry behavior tag comprises a candidate tag and a corresponding candidate session identifier;

responding to the confirmation operation aiming at the configuration information of the group entry behavior tag, and generating a group entry behavior matching strategy based on the configuration information of the group entry behavior tag to obtain the tag matching strategy; the matching strategy of the group entering behavior is used for determining that a user label corresponding to the current user identification is a candidate label corresponding to the candidate session identification which is successfully matched when the target session identification and the candidate session identification are successfully matched, and the target session identification is the session identification corresponding to the target group entering behavior in the user behavior data corresponding to the current user identification.

6. The method according to claim 5, wherein the configuration information of the grouping behavior tags further includes a reference grouping manner corresponding to the candidate tags, and the displaying the configuration information of the grouping behavior tags in response to the configuration operation of the grouping behavior tags in the configuration area of the grouping behavior tags of the policy configuration interface includes:

7. The method of claim 2, wherein prior to determining that a tag matches a policy in response to a configuration operation triggered at the policy configuration interface, the method further comprises:

displaying a data uploading interface;

uploading a plurality of candidate push data in the data uploading interface;

the determining a tag matching policy in response to the configuration operation triggered at the policy configuration interface includes:

in an interaction behavior tag configuration area of the strategy configuration interface, responding to configuration operation of an interaction behavior tag, and displaying interaction behavior tag configuration information; the interaction behavior tag configuration information comprises candidate tags, corresponding candidate push data and candidate interaction behavior information;

responding to the confirmation operation aiming at the interactive behavior tag configuration information, and generating an interactive behavior matching strategy based on the interactive behavior tag configuration information to obtain the tag matching strategy; the interaction behavior matching strategy is used for determining that a user tag corresponding to a current user identifier is a candidate tag corresponding to candidate push data which is successfully matched when push data corresponding to a target interaction behavior is successfully matched with the candidate push data and interaction behavior information corresponding to the candidate push data which is successfully matched with the target interaction behavior is also successfully matched with the candidate interaction behavior information corresponding to the candidate push data which is successfully matched with the target interaction behavior, and the target interaction behavior is acquired from the user behavior data corresponding to the current user identifier.

8. The method according to any one of claims 1 to 7, wherein the displaying the push configuration information in response to the configuration operation of data push comprises:

displaying a push task configuration interface;

responding to a push data selection operation triggered on the push task configuration interface, and determining the data to be pushed;

and determining the target user tag in response to a user tag selection operation triggered on the push task configuration interface.

9. The method of claim 8, wherein the push configuration information further includes at least one of a target push manner and a target relay user identifier, and the displaying the push configuration information in response to the configuration operation of the data push includes:

responding to a transit user identifier selection operation triggered on the push task configuration interface, and determining the target transit user identifier; the transfer terminal is a user terminal corresponding to the target transfer user identifier;

and determining the target pushing mode in response to a pushing mode selection operation triggered on the pushing task configuration interface.

10. A data pushing method is applied to a transit terminal, and the method comprises the following steps:

11. The method according to claim 10, wherein the data pushing task sent by the display management terminal comprises:

responding to the starting operation of the associated application corresponding to the target application, and displaying a session management interface; the session management interface displays a session entrance of a management session interface of the transit terminal and the management terminal;

responding to a trigger operation aiming at the session entrance, and entering the management session interface;

and displaying the data pushing task in the management session interface.

12. The method of claim 10, further comprising:

responding to the session sharing operation aiming at the data to be pushed, and displaying a session sharing configuration interface; the session sharing configuration interface comprises a user tag configuration area;

displaying a target user tag in response to a configuration operation for the user tag configuration area;

and responding to a sharing confirmation operation aiming at the data to be pushed, sending the data to be pushed to a target session interface as a target session message, wherein the target session interface is a session interface of the transfer terminal and the target user terminal in an associated application corresponding to the target application.

13. The method of claim 10, further comprising:

responding to the dynamic information sharing operation aiming at the data to be pushed, and displaying a dynamic information sharing configuration interface; the dynamic information sharing configuration interface comprises a user tag configuration area;

and responding to sharing confirmation operation aiming at the data to be pushed, sending the data to be pushed to the target user terminal as target dynamic information so as to display the target dynamic information on a dynamic information display interface of the target application at the target user terminal.

14. The method of claim 10, further comprising:

displaying a session creation interface; the session creation interface comprises a user tag configuration area;

determining a target user tag in response to a configuration operation for the user tag configuration area;

responding to the creation operation of a session group, establishing a target session group corresponding to the target user tag, generating group-entering invitation information corresponding to the target session group, and sending the group-entering invitation information to a target session interface, wherein the target session interface is a session interface of the transit terminal and the target user terminal in an associated application corresponding to the target application.

15. A tag processing method applied to a first server, the method comprising:

16. The method of claim 15, wherein the user behavior data is obtained in at least one of the following manners, including:

pulling a session record of a current user identifier and an associated application session object from a second server corresponding to the associated application of the target application, extracting a session message of which a message sender is the current user identifier from the session record as an initial session message, and obtaining user behavior data corresponding to the current user identifier based on the initial session message;

receiving a group entering behavior message sent by the second server through a callback interface, and obtaining user behavior data corresponding to the current user identifier based on the group entering behavior message; the group entering behavior message carries the session identification of the session group which is added by the current user identification;

acquiring buried point data reported by a current user terminal corresponding to the current user identifier, and acquiring user behavior data corresponding to the current user identifier based on the buried point data; the buried point data is obtained by detecting the interaction behavior of the current user identification acting on the push data.

17. The method of claim 16, wherein obtaining the user behavior data corresponding to the current user identifier based on the group entry behavior message comprises:

18. The method of claim 15, wherein determining the user label corresponding to each user identifier based on the user behavior data comprises:

extracting target behavior data from the user behavior data based on policy reference information corresponding to a tag matching policy;

storing the target behavior data into a message queue;

and reading the target behavior data from the message queue, and performing label matching processing on the target behavior data based on the label matching strategy to obtain user labels corresponding to the user identifications.

19. The method of claim 18, wherein the target behavior data comprises different types of target behavior data, each type having a corresponding message queue and tag matching policy, and wherein storing the target behavior data into a message queue comprises:

storing the target behavior data of the same type into a corresponding message queue;

the reading the target behavior data from the message queue, and performing tag matching processing on the target behavior data based on the tag matching policy to obtain the user tags corresponding to the user identifiers includes:

and reading corresponding target behavior data from the message queue of the current type, and performing label matching processing on the corresponding target behavior data based on a label matching strategy corresponding to the current type to obtain user labels of the user identifications corresponding to the current type.

20. The method of claim 18, wherein extracting target behavior data from the user behavior data based on policy reference information corresponding to the tag matching policy comprises:

when the tag matching strategy is a keyword matching strategy, taking a target transit user identification in the keyword matching strategy as corresponding strategy reference information, acquiring an intermediate conversation message from user behavior data corresponding to a current user identification as a reference conversation message, and taking the reference conversation message as target behavior data corresponding to the current user identification; the message receiver and the message sender corresponding to the intermediate session message are respectively a target transfer user identifier and a current user identifier;

when the tag matching strategy is a grouping behavior matching strategy, taking a candidate session identifier in the grouping behavior matching strategy as corresponding strategy reference information, acquiring a grouping behavior message and a grouping mode corresponding to the candidate session identifier from user behavior data corresponding to the current user identifier as target grouping behaviors, and taking the target grouping behaviors as target behavior data corresponding to the current user identifier;

and when the tag matching strategy is an interaction behavior matching strategy, taking candidate push data in the interaction behavior matching strategy as corresponding strategy reference information, acquiring buried point data corresponding to the candidate push data from user behavior data corresponding to the current user identification as a target interaction behavior, and taking the target interaction behavior as target behavior data corresponding to the current user identification.

21. The method according to claim 20, wherein performing tag matching processing on the target behavior data based on the tag matching policy to obtain a user tag corresponding to each user identifier includes:

when the tag matching strategy is a keyword matching strategy, matching the reference session message with each candidate keyword, and taking a candidate tag corresponding to the candidate keyword which is successfully matched as a user tag corresponding to the current user identifier;

when the tag matching strategy is a matching strategy of the group entering behaviors, matching the group entering mode corresponding to the target group entering behavior with each intermediate group entering mode, and taking a candidate tag corresponding to the intermediate group entering mode which is successfully matched as a user tag corresponding to the current user identifier; the session identification corresponding to the target group entering behavior is consistent with the candidate session identification corresponding to the intermediate group entering mode;

when the tag matching strategy is an interaction behavior matching strategy, matching interaction behavior information corresponding to the target interaction behavior with each piece of intermediate interaction behavior information, and taking a candidate tag corresponding to the successfully-matched intermediate interaction behavior information as a user tag corresponding to the current user identifier; and the candidate push data corresponding to the intermediate interaction behavior information is consistent with the push data corresponding to the target interaction behavior.

22. A data push system is characterized by comprising a first server, a management terminal, a transfer terminal and a target user terminal;

23. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 9 or 10 to 14 or 15 to 21.

24. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 9 or 10 to 14 or 15 to 21.

25. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method of any one of claims 1 to 9 or 10 to 14 or 15 to 21 when executed by a processor.