CN108881339B - Push method, user tag generation method, device and equipment - Google Patents
Push method, user tag generation method, device and equipment Download PDFInfo
- Publication number
- CN108881339B CN108881339B CN201710329231.0A CN201710329231A CN108881339B CN 108881339 B CN108881339 B CN 108881339B CN 201710329231 A CN201710329231 A CN 201710329231A CN 108881339 B CN108881339 B CN 108881339B
- Authority
- CN
- China
- Prior art keywords
- user
- task
- tag
- push task
- identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0631—Item recommendations
Abstract
The embodiment of the invention discloses a pushing method, a user label generating method, a device and equipment, wherein the method comprises the following steps: when detecting that connection is established with a client of a user, acquiring an identifier of the user; determining an identifier of a current push task; determining a correlation index between a user tag of the user and a tag of the push task according to the identifier of the user and the identifier of the push task, wherein the user tag is generated by behavior data of the user; if the association index meets a preset first condition, pushing the pushing task to the client; receiving feedback information of the user on the pushing task, which is sent by the client; and modifying the association index between the user label of the user and the label of the pushing task according to the feedback information.
Description
Technical Field
The invention relates to a mobile internet technology, in particular to a pushing method, a user tag generation device and user tag generation equipment.
Background
In a conventional operation method, generally, an operator specifies some key information according to the characteristics of a pushing task, filters the accumulated user information, and generates a user set by users meeting the conditions, so as to associate the user set with the operation task. When a user accesses the background system, whether the user is located in a target user set of a certain operation task is searched according to user identification (ID, Identity), and if the user is located, the operation task is pushed.
The conventional methods have problems in that: the efficiency is low; usually, the operation tasks are very many, each task needs to manually extract the user list, and the labor cost is high. In addition, conventional methods also do not take user feedback into account, which may cause annoyance to more users, resulting in a reduction in product public praise.
Disclosure of Invention
In view of this, embodiments of the present invention provide a pushing method, a user tag generation method, a device and an apparatus for solving at least one problem in the prior art.
The technical scheme of the embodiment of the invention is realized as follows:
the embodiment of the invention provides a pushing method, which comprises the following steps:
when detecting that connection is established with a client of a user, acquiring an identifier of the user;
determining an identifier of a current push task;
determining a correlation index between a user tag of the user and a tag of the push task according to the identifier of the user and the identifier of the push task, wherein the user tag is generated by behavior data of the user;
if the association index meets a preset first condition, pushing the pushing task to the client;
receiving feedback information of the user on the pushing task, which is sent by the client;
and modifying the association index between the user label of the user and the label of the pushing task according to the feedback information.
The embodiment of the invention provides a method for generating various user tags, which further comprises the following steps:
detecting the network behavior of the user using the terminal, and extracting keywords of an access object of the network behavior;
if the keyword is in the preset tag library, taking the keyword as a user tag of the user, wherein the preset tag library is configured manually;
determining a corresponding weight for the user tag;
and storing the user tags of the users according to a preset storage structure, wherein the storage structure at least comprises the weights and the user tags.
An embodiment of the present invention provides a server, including a memory, a processor, and a computer program stored on the memory and capable of running on the processor, where the processor implements the push method when executing the program.
The embodiment of the invention provides a terminal, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor executes the program to realize the user label generation method.
An embodiment of the present invention provides a push apparatus, where the apparatus includes:
the first detection unit is used for acquiring the identification of a user when detecting that the connection is established with the client of the user;
the first determining unit is used for determining the identifier of the current push task;
a second determining unit, configured to determine, according to the identifier of the user and the identifier of the push task, an association index between a user tag of the user and a tag of the push task, where the user tag is generated by behavior data of the user;
the pushing unit is used for pushing the pushing task to the client if the association index meets a preset first condition;
the first receiving unit is used for receiving feedback information of the user on the pushing task, which is sent by the client;
and the modifying unit is used for modifying the association index between the user label of the user and the label of the pushing task according to the feedback information.
The embodiment of the invention provides a device for generating a user label, which further comprises:
the second detection unit is used for detecting the network behavior of the user using the terminal and extracting keywords of an access object of the network behavior;
a fourth determining unit, configured to, if the keyword is in the preset tag library, use the keyword as a user tag of the user, where the preset tag library is configured manually;
a fifth determining unit, configured to determine a corresponding weight for the user tag;
a storage unit, configured to store a user tag of the user according to a preset storage structure, where the storage structure at least includes the weight and the user tag;
and the first sending unit is used for sending the user tags with the weights meeting the preset second condition to the server.
The embodiment of the invention provides a pushing method, a user tag generation method, a device and equipment, wherein when connection with a client of a user is detected, an identifier of the user is obtained; determining an identifier of a current push task; determining a correlation index between a user tag of the user and a tag of the push task according to the identifier of the user and the identifier of the push task, wherein the user tag is generated by behavior data of the user; if the association index meets a preset first condition, pushing the pushing task to the client; receiving feedback information of the user on the pushing task, which is sent by the client; modifying the association index between the user label of the user and the label of the pushing task according to the feedback information; therefore, behavior feedback of the user to the popularization task is collected, and the feedback can adjust a target user group, so that negative influence on the user is reduced.
Drawings
Fig. 1A is a schematic flow chart illustrating an implementation of a push method according to an embodiment of the present invention;
FIG. 1B is a diagram of a network architecture according to an embodiment of the present invention;
FIG. 1C is a schematic diagram of a client interface according to an embodiment of the invention;
fig. 2 is a schematic flow chart illustrating an implementation of a user tag generation method according to an embodiment of the present invention;
fig. 3 is a schematic flow chart illustrating an implementation of a push method according to an embodiment of the present invention;
fig. 4A is a schematic structural diagram of a pushing device according to an embodiment of the present invention;
fig. 4B is a schematic structural diagram of a push device according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a hardware entity of a computing device according to an embodiment of the present invention.
Detailed Description
The technical solution of the present invention is further elaborated below with reference to the drawings and the specific embodiments.
The embodiment of the invention provides a push method, which is applied to a server, wherein the functions realized by the method can be realized by calling a program code through a processor in the server, and the program code can be saved in a computer storage medium.
Fig. 1A is a schematic diagram of an implementation flow of a push method according to an embodiment of the present invention, and as shown in fig. 1A, the method includes:
step S101, when a server detects that connection is established with a client of a user, acquiring an identifier of the user;
in this embodiment, the client includes a web page client, a browser, an Application program (APP, Application for short), and the like, where the Application program may be other applications such as an instant messaging Application, a social Application, a shopping Application, and a financial Application, and the client may further include any parent program and any child program. Correspondingly, the client establishes connection including login of APP, access of browser, access or login of applet (mini program), and the like. The following introduces a parent program and a child program, wherein the child program is a web-based application developed based on a hypertext markup language, a cascading style sheet and a script language, and is operated in the parent program in the form of a web page. The parent program comprises an instant messaging or social application or client, such as a WeChat application. The sub-program is a Web-based application (Web APP) developed based on hypertext Markup Language (HTML) 5, Cascading Style Sheets (CSS3, screening Style Sheets), and JavaScript, and runs in the main program in the form of a Web page, for example, a public number sub-program based on HTML5, also referred to as H5 APP. In the implementation process, the subroutine can be implemented by using H5 APP. The application in which the sub program runs is called a parent program. In some cases, a sub-program is also referred to as a web application, e.g., an applet, which is an application that can be used without downloading and installing, and which implements the illusion that the application is "within reach" and can be opened by a user scanning or searching for a scan. Since the subprogram itself does not need to be installed and uninstalled, the subprogram also embodies the idea of "go-and-go-after-use".
In this embodiment, the identifier of the user may be an account, a temporary Number, a terminal identifier, and the like of the user, the account may be information for identifying the user, such as a Mobile phone Number, a mailbox, and the like of the user, the identifier of the user may also be a unique code allocated to the user by the server, the code may be allocated within a period of time, and may be information for identifying the user, which is allocated according to different Internet Protocol (IP) addresses, terminals, and the like, and the identifier of the terminal may include an International Mobile Subscriber Identity (IMSI), an International Mobile Equipment Identity (IMEI), and the like.
Step S102, the server determines the identification of the current push task;
in this embodiment, step S102 and step S101 are not sequentially executed, and step S102 may be executed before step S101 or after step S101, for example, when it is detected that a connection is established with a client of a user, an identifier of the user is obtained, and then an identifier of a current push task is obtained.
In this embodiment, the identifier of the push task may be information such as a name and a number of the push task, where the push task may be a promotional message, where the promotional message may be a common text message, and may be a multimedia message, such as an advertisement.
Step S103, the server determines a correlation index between a user label of the user and a label of the push task according to the identification of the user and the identification of the push task, wherein the user label is generated by behavior data of the user;
in this embodiment, the association index is used to characterize a parameter between the user tag and the tag of the push task, where the association is close. The association index may be embodied in the form of a white list, or a black list, or a white list and a black list associated with the identifier, where the identifier may be an identifier of a user or an identifier of a push task. When the association index adopts a white list, for example, the association index can be a white list about the identification of the user, and if the identification of the user is on the white list, the association index is pushed to the user; yet another example may be a white list including an identification of the push task, and if the identification of the push task is on the white list, the user may be pushed with the task. In order to avoid harassment to the user, if the user clearly does not want to receive the promotion task, the promotion task is not pushed to the user.
In the implementation process, the association index may also be represented by a weight value, for example, if the tag of the push task is consistent with the tag of the user, the tag of the push task has a tag of "car", but the weight value of the tag of "car" in the tag of the user is 0 or a negative value, that is, if the user does not like the car, then the car-type advertisement should not be recommended to the user; for example, the labels of the push tasks are consistent with the labels of the users, and the labels of the "property" are provided, but the weight value of the label of the "property" in the labels of the users is 1, that is, the users like the property, then the property advertisement can be recommended to the users.
In this embodiment, the white list of the correlation indexes indicates that the correlation indexes meet a first condition, and the black list indicates that the correlation indexes do not meet a preset first condition. In order to improve the accuracy of describing the association, the number of times of the white list or the black list can be used for representing the association. In other embodiments, the association index may also be represented by whether the user tag is consistent with or matched with the tag of the push task, and if the user tag is consistent with or matched with the tag of the push task, the push task is pushed to the client, and if the user tag is inconsistent with or not matched with the tag of the push task, the push task is pushed to the client.
Step S104, if the correlation index meets a preset first condition, the server pushes the pushing task to the client;
step S105, the server receives feedback information of the user to the pushing task, wherein the feedback information is sent by the client;
and step S106, the server modifies the association index between the user label of the user and the label of the pushing task according to the feedback information.
In this embodiment, the association index in step S106 is consistent with that in step S103, that is, the association index may be a black and white list or a weight.
In this embodiment, after the client receives the push task, the user may have a feedback behavior for the task, where the feedback behavior includes an active behavior and a non-active behavior of the user, and the active behavior may be a positive behavior and a negative behavior, and the non-active behavior is generally a negative behavior, for example, the promotion task is a house advertisement, the client of the user receives the house advertisement, the client displays the house advertisement to the user, and the user cannot place the advertisement, and in the whole process of browsing the page, the user does not click the advertisement, and the non-active behavior of the user is a negative behavior. This behavior by the user is also a negative behavior if the user clicks on the close option on the advertisement. This behavior of the user is a positive behavior if the user clicks on an advertisement and makes a view. The client monitors feedback information of the user to the promotion task, namely, monitors feedback behavior of the user to the promotion task, then takes the feedback behavior of the user as record as feedback information, wherein the feedback information comprises positive feedback information and negative feedback information, the positive feedback information is information representing that the user completes the task, the negative feedback information is information representing that the user does not complete the task, for example, information representing that the user directly closes the pushed task, and the like, and finally the client sends the feedback information of the user to the pushed task to the server.
In this embodiment, as shown in fig. 1B, a user uses a terminal, such as a client on a mobile phone, to establish a connection with a server (S1 connection), for example, the user browses his/her friend circle with the mobile phone, the server 20 pushes the push task to the client through the above steps S101 to S104 (S2 connection), referring to fig. 1C, it is assumed that the push task is to push an advertisement 30 of a shared bicycle to a friend circle 33 of the user, the client displays the advertisement of the shared bicycle to the user after receiving the advertisement of the shared bicycle, and then, after seeing the advertisement of the shared bicycle, the user does not manage the advertisement, and continues to browse his/her friend circle, and in the whole browsing process, the user does not click the advertisement, and the client feeds back negative feedback information to the server. If the user clicks on the close option 31 on the advertisement, the client feeds back negative feedback information to the server. If the user clicks on the advertisement and makes a view 32, the client feeds back positive feedback information to the server. Thus, the server collects feedback information of the user on the promotion task (step S105), and the server adjusts the correlation index according to the feedback information, so as to adjust a target user group of the next task pushing, thereby reducing negative effects on the user.
In other embodiments of the present invention, the modifying the association index between the user tag of the user and the tag of the push task according to the feedback information includes:
if the feedback information is positive feedback information, increasing the association index between the user label of the user and the label of the pushing task; if the feedback information is negative feedback information, reducing the association index between the user label of the user and the label of the pushing task; and if the feedback information is negative feedback information, reducing the association index between the user label of the user and the label of the pushing task.
If the association index is only represented by a white list or a black list, reducing the association index between the user tag of the user and the tag of the push task may be to remove the user identifier or the push task identifier from the white list, or to keep the identifier on the black list; if the association index is represented by only a white list and a black list, decreasing the association index between the user's user tag and the tag of the push task may be to remove the user's identity from the white list and add it to the black list, or to continue to maintain the black list. If the association index is only represented by a white list, increasing the association index between the user tag of the user and the tag of the push task can be to continuously maintain the user identifier or the push task identifier in the white list; if the association indication is only represented by a black list, increasing the association index between the user tag of the user and the tag of the push task may be to remove the user identifier or the push task identifier from the black list; if the association index is represented by only a white list and a black list, decreasing the association index between the user tag of the user and the tag of the push task may be to remove the user's identity from the black list and add it to the white list, or to continue to maintain the white list.
In other embodiments of the present invention, in order to further accurately describe the association index, the association index includes a number of times corresponding to a white list and a number of times corresponding to a black list, where the preset first condition is that the preset number of times is less than that of the black list; if the feedback information is negative feedback information, reducing the association index between the user label of the user and the label of the pushing task, including:
if the feedback information indicates that the user closes the push task or does not respond to the push task, determining the feedback information as negative feedback information; if the user identification is in the white list of the pushing task and the number of times that the user identification is in the white list of the pushing task is larger than a minimum threshold value, reducing the number of times of the white list; if the number of times that the user identification is in the white list of the push task is the lowest threshold value, placing the user identification in the black list of the push task; and if the user identification is in the blacklist of the push task, increasing the times of the white list.
If the feedback information is positive feedback information, increasing the association index between the user label of the user and the label of the pushing task, including: if the feedback information indicates that the user responds to the push task, determining that the feedback information is positive feedback information; if the user identifier is in the blacklist of the push task and the number of times that the user identifier is in the blacklist of the push task is greater than a minimum threshold value, reducing the number of times of the blacklist; if the number of times that the user identification is in the blacklist of the push task is the lowest threshold value, placing the user identification in the white list of the push task; and if the user identification is in the white list of the pushing task, increasing the times of the white list.
In other embodiments of the present invention, the determining, according to the identifier of the user and the identifier of the push task, an association index between a user tag of the user and a tag of the push task, and if the association index meets a preset first condition, pushing the push task to the client includes:
step S11, obtaining the user label of the user according to the user identification, wherein the user label is generated by the behavior data of the user;
in this embodiment, the manner of obtaining the user tag in step S11 includes two ways, one is that the server queries the local cache to check whether the tag concerned by the user is stored, and the other is that the server obtains the tag by using a request response manner.
Step S12, determining the label of the push task according to the push task identifier;
in this embodiment, the determining the tag of the push task according to the identifier of the push task includes: and searching a preset association list according to the identifier of the push task to obtain the push task. In other embodiments of the present invention, the method further comprises a process of forming an association list, see steps S21 and S22 below.
Step S13, if the user tag matches with the tag of the push task, determining that the association index meets the preset first condition, and pushing the push task to the client.
In an embodiment of the present invention, the obtaining a user tag of the user according to the identifier of the user includes: searching a label concerned by the user in a local cache according to the identification of the user; and if the label of the pushing task is matched with the label concerned by the user, determining that the association index meets the preset first condition, and pushing the pushing task to the client.
In an embodiment of the present invention, the obtaining a user tag of the user according to the identifier of the user includes: sending a user tag request to the client, wherein the tag request is used for requesting a user tag; and receiving a user tag response sent by the client, wherein the user tag response carries a user tag.
The embodiment of the invention also comprises a process of forming the association list, therefore, the method also comprises the following steps:
step 21, determining a tag of the push task from a preset tag library for the push task according to the attribute of the push task;
in this embodiment, the attributes of the push task at least include one of the following information, a title, a content, classification information, and the like of the push task, and a keyword may be extracted from the above information as a tag, in order to prevent the keyword from being too many and unrepresentative, a preset tag library may be preset, and the preset tag library may be a large list of operation-focused tags customized for an operator, and is recorded as S _ ALL, where the list mainly comes from an artificial experience value, and prevents a tag cache of a user from being too large. If the pushing task is shopping, the label of the pushing task can be marked with a label of shopping; if the pushing task is news, extracting keywords according to the titles and abstracts of the news, wherein the keywords can be used as labels; if the push task is a video, the name of the video, actors, director, etc. may be labels.
In this embodiment, step S21 may also have an alternative method, that is, receiving a configuration operation of an operator on the push task, and determining a tag of the push task for the push task according to the configuration operation; the embodiment of the invention configures the operation task by using the label set, and the operator only needs to input the label and does not need to extract the user list from the offline data, thereby improving the efficiency.
Step 22, the server establishes an association list between the identifier of the push task and the tag of the push task;
in this embodiment, the association list is used to represent a mapping relationship between the identifier of the push task and the tag of the push task, and generally, a push task at least includes one tag, so the mapping relationship is a one-to-one mapping or a one-to-many mapping.
And step 23, searching a preset association list according to the identifier of the push task to obtain the push task.
Step 23 provides a method for implementing the determining of the tag of the push task according to the identifier of the push task.
In the step S21, the determining, according to the attribute of the push task, a tag of the push task from a preset tag library includes:
step S211, determining the keywords of the push task according to the content of the push task;
step S212, if the keyword is in the preset tag library, the keyword is used as a tag of the pushing task, wherein the preset tag library is configured manually.
An embodiment of the present invention further provides a method for generating a user tag, fig. 2 is a schematic flow chart illustrating an implementation of the method for generating a user tag according to the embodiment of the present invention, and as shown in fig. 2, the method further includes:
step S201, a terminal detects the network behavior of the user using the terminal and extracts keywords of an access object of the network behavior;
in this embodiment, the user tag of the user is generated according to the keyword (key information) of the user, and the user tag is generated by the network behavior data of the user, for example, the user frequently visits panning, and the user can automatically play a keyword for shopping; a user browses a page and extracts keywords of a title and an abstract of the page; the user views the video, wherein the name, actors, director, etc. of the video may be the keywords.
Step S202, if the keyword is in the preset tag library, the terminal takes the keyword as a user tag of the user, wherein the preset tag library is configured manually;
in this embodiment, the keywords of the user are collected in the step S201: when a user accesses a webpage, analyzing information such as a website type, a webpage title and a webpage keyword, extracting feature words in the information as the keywords of the user, and if the keywords are not in S _ ALL, directly discarding the keywords. The labels can mark the interest and concern of the user, and the click rate and complaints of the operation tasks related to the labels pushed by the user are high.
Step S203, the terminal determines corresponding weight for the user label;
in this embodiment, if it is the first addition, setting weight to 1, the label (tag) already existing may be represented by the following formula:
weight (new) ═ weight (old) - (current time-update) × X + Y;
wherein, X is a time attenuation coefficient, Y is a weight number added once, uptime represents the latest updating time, weight (new) represents the current weight, and weight (old) represents the previous weight. If weight (old) - (current time-update) X is less than 0, delete the tag, or set weight to 1 directly. In this embodiment, the weight of the tag changes with time, and therefore, a method for changing the weight of the tag is also provided in the embodiment of the present invention. Therefore, the user tags can be generated by real-time data, one user corresponds to one tag set, a plurality of user sets do not need to be stored, and the consumption of the memory of the terminal is reduced. In other embodiments of the present invention, the method further comprises: the terminal sends the user tag and the user identification to the server together, and the server caches the user tag locally. Meanwhile, when the weight of a certain tag is 0 or less than 0 as time passes, indicating that the user has disliked the content, the tag is deleted. Therefore, on one hand, the user tags are increased due to the fact that the network behaviors of the users are monitored, on the other hand, the user tags are reduced along with the time, and therefore the local caches of the terminal and the server side can be reduced.
Step S204, the terminal stores the user label of the user according to a preset storage structure, wherein the storage structure at least comprises the weight and the user label.
In other embodiments of the present invention, the method further comprises: receiving a user tag request sent by the server, wherein the user tag request is used for requesting a user tag; and responding to the user tag request, carrying the user tag with the weight meeting a preset second condition in the user tag response, and sending the user tag response to the server.
The technical scheme provided by the embodiment of the invention is mainly used in an operation system of a product. Product operations typically push information to a user side, and if the user has no interest in the pushed information at all, the user is considered to be harassed. The embodiment of the invention provides a technical scheme, which can realize the commercialization and the user public praise at the same time.
An embodiment of the present invention provides a push method, and fig. 3 is a schematic diagram illustrating an implementation flow of the push method according to the embodiment of the present invention, where as shown in fig. 3, the method includes:
step S301, configuring a user tag white list by an operator;
here, an operator performs a first configuration operation on an operation system, where the first configuration operation is used to configure a white list of a user tag, then the operation system receives the first configuration operation of the operator, determines the white list of the user tag according to the first configuration operation of the operator, and sends the white list of the user tag to the user system.
Step S302, browsing a website by a user;
here, the user browses a website on the user system;
step S303, the user system extracts key information;
here, the user system extracts key information of the user according to the behavior of the user to browse the website;
step S304, generating a user label of the user according to the key information of the user;
here, a user tag of the user is generated according to the key information of the user, and the user tag is generated by behavior data of the user, for example, the user frequently visits a treasure, and the user can automatically make a tag for shopping; a user browses a page, and extracts keywords of a title and an abstract of the page, wherein the keywords can be used as tags; the user views the video, where the name, actors, director, etc. of the video may serve as tags. The labels can mark the interest and concern of the user, and the click rate and complaints of the operation tasks related to the labels pushed by the user are high.
Step S305, the user system generates a user characteristic library;
here, the user system generates a user feature library according to the user tag;
step S306, configuring an operation task by an operator;
here, the operator performs a second configuration operation on the operation system, the second configuration operation being used for configuring the operation task, and then the operation system receives the second configuration operation of the operator, and the operation system determines the operation task according to the second configuration operation of the operator.
Step S307, the operator designates a label concerned by the task;
here, the operator performs a third configuration operation on the operation system, the third configuration operation being used to specify the tag of the task attention, and then the operation system receives the third configuration operation of the operator, and the operation system determines the tag of the task attention according to the third configuration operation of the operator.
Step S308, the user is connected to the operation system;
here, the user connects the user system to the operating system.
Step S309, the operation system traverses the online task;
step S310, the operation system judges whether the user has the label concerned by the task;
step S311, the operation system obtains a user tag list;
here, the operating system sends a user tag list request to the user system, where the request is used to obtain a user tag list;
step S312, the user system returns a user tag list;
here, the user system receives a user tag list request and then the user system returns the user tag list.
Step S313, the operation system determines the label that the user has the task attention according to the user label list;
the operation system judges whether the user has a label concerned by the task according to a user label list returned by the user system, and if the user is determined to have the label concerned by the task, the operation system issues the task to the user system;
step S314, the operation system issues tasks;
here, the running system issues tasks to the user system;
step S315, the user A directly closes the pushed task;
here, the user system monitors feedback information of the user to the task, where the feedback information includes positive feedback information and negative feedback information, where the positive feedback information is information representing that the user completes the task, and the negative feedback information is information representing that the user does not complete the task, such as information representing that the user directly closes a pushed task. And the user system sends the monitored feedback information to the operation system.
Step S316, the operation system generates a task label blacklist;
the operation system receives feedback information generated by the user system, then judges whether the feedback information of the user is positive feedback information, if the feedback information is positive feedback information (for example, information of the user completing a task), the operation system keeps that a label of the user is a white list on the task, and if the feedback information of the user is not positive feedback information but negative feedback information (if the user directly closes the pushed task), the operation system generates a task label black list.
Step S317, connecting the user to an operation system;
step S318, when the operating system determines whether the task is issued, the blacklist condition needs to be considered.
In other embodiments of the present invention, the operator configures the operation task and only needs to input the tag list in selecting the target user. And after the online, the operation system automatically selects the users according to the labels configured by the tasks.
In other embodiments of the present invention, when a user receives an operation task, if the task is directly closed, all tags of the user are recorded in the blacklist of the operation task. When the number of times that a label is recorded in the blacklist reaches a certain number, other subsequent users will not push the operation task if the label is included.
In other embodiments of the present invention, a custom operation attention tag large list is recorded as S _ ALL, and the list mainly comes from a manual experience value, so as to prevent the tag cache of the user from being too large.
Collecting user tags of other embodiments of the invention may include: when a user accesses a webpage, key information such as website types, webpage titles and webpage keywords is analyzed, feature words in the key information are extracted as features of the user, and if the features are not in S _ ALL, the features are directly discarded. If the feature is in S _ ALL, the feature is tagged as a user. Therefore, the embodiment of the invention provides a method for automatically generating a user tag.
In other embodiments of the present invention, a process for updating a user tag is also provided, the process comprising: defining a tag storage structure, in other embodiments, the tag storage structure may be expressed as: { tag, update time, latest update time, weight }. The first addition, setting weight to 1, can be expressed for an already existing tag by the following formula:
weight (new) ═ weight (old) - (current time-update) × X + Y;
wherein, X is a time attenuation coefficient, Y is a weight number added once, uptime represents the latest updating time, weight (new) represents the current weight, and weight (old) represents the previous weight. If weight (old) - (current time-update) X is less than 0, weight is directly set to 1. In this embodiment, the weight of the tag changes with time, and therefore, a method for changing the weight of the tag is also provided in the embodiment of the present invention.
In other embodiments of the present invention, the operation task is configured, and the tag list that needs to be paid attention to is configured for the task, which may be a manual mode or an automatic mode, that is, an operator configures the operation task and configures the tag list that needs to be paid attention to for the task. And an automatic mode is adopted, namely after the operation system receives the tasks sent by other equipment or acquires the tasks, the operation system allocates labels needing attention to the tasks according to the attributes of the tasks, wherein the attributes of the tasks can be keywords of the tasks.
In other embodiments of the present invention, the user is online, and the operating system obtains the tag information of the user in the cache according to the user ID, and records the tag information as u _ tag.
In other embodiments of the present invention, the operation system sequentially detects the tag of interest configured for the operation task, and checks whether the user includes the tag; if not, the process is continuously repeated, namely, the concerned label configured by the operation task is continuously detected, and whether the user contains the label is checked; if so, calculating the current weight according to the following formula according to the information of the tag in the u _ tag:
weight (new) ═ weight (old) - (current time-update) × X + Y;
if weight >0, the user meets the issuing condition and issues the task.
In other embodiments of the present invention, the user receives the operation task, and if the task prompt is directly closed, the system acquires all the tags of the user after receiving the reported data, excludes the tag concerned by the task, and adds the remaining tags into the operation task operation tag blacklist. The black list stores the format tag count, indicating that each tag was added several times.
In other embodiments of the present invention, when a certain operation task has a label blacklist, when determining whether to issue a task to a user, the situation that the label of the user is in the blacklist needs to be considered, if the total number of counts corresponding to the label of the user in the blacklist exceeds a specified threshold, the task is not issued to the user.
It can be seen from the above that, in the method for operating the feature tag provided in the embodiment of the present invention, the operation task does not need to manually obtain the user list, so that the operation efficiency is improved. Further, the embodiment of the invention provides a method for automatically generating a user label and a method for changing label weight; the labels are stored according to people, so that the memory space is saved, and the precision of operation is improved. In addition, the embodiment of the invention provides a blacklist strategy aiming at the operation task, and records the implicit negative feedback information of the user. Due to the existence of the blacklist, the feedback of the user who has received the task is used for the condition of pushing the task to other users later, so that the operation accuracy can be improved, and the reduction of product public praise is avoided.
Based on the foregoing embodiments, embodiments of the present invention provide a pushing apparatus, where each unit included in the pushing apparatus and each module included in each unit may be implemented by a processor in a server, such as a computer, a service cluster, a personal computer, or the like, or may be implemented by a logic circuit; in the course of an embodiment, the processor may be a Central Processing Unit (CPU), a Microprocessor (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like.
Fig. 4A is a schematic structural diagram of a pushing device according to an embodiment of the present invention, and as shown in fig. 4A, the pushing device 400 includes:
a first detecting unit 401, configured to obtain an identifier of a user when detecting that a connection is established with a client of the user;
a first determining unit 402, configured to determine an identifier of a current push task;
a second determining unit 403, configured to determine, according to the identifier of the user and the identifier of the push task, an association index between a user tag of the user and a tag of the push task, where the user tag is generated by behavior data of the user;
a pushing unit 404, configured to push the pushing task to the client if the association index meets a preset first condition;
a first receiving unit 405, configured to receive feedback information of the user on the push task, where the feedback information is sent by the client;
a modifying unit 406, configured to modify, according to the feedback information, an association index between the user tag of the user and the tag of the push task.
In another embodiment of the present invention, the modifying unit is configured to reduce an association index between the user tag of the user and the tag of the push task if the feedback information is negative feedback information.
In other embodiments of the present invention, the feedback information includes positive feedback information and negative feedback information, and the modifying unit is configured to increase an association index between a user tag of the user and a tag of the push task if the feedback information is the positive feedback information; and if the feedback information is negative feedback information, reducing the association index between the user label of the user and the label of the pushing task.
In other embodiments of the present invention, the association index includes a number of times corresponding to a white list and a number of times corresponding to a black list, where the preset first condition is that the preset number of times is smaller than the preset number of times of the black list; the modification unit comprises a first determination module, a first processing module and a second processing module, wherein:
a first determining module, configured to determine that the feedback information is negative feedback information if the feedback information indicates that the user closes the push task or does not respond to the push task;
a first processing module, configured to reduce the number of times of the white list if the identifier of the user is in the white list of the push task and the number of times of the identifier of the user is in the white list of the push task is greater than a minimum threshold; if the number of times that the user identifier is in the white list of the push task is the lowest threshold value, placing the user identifier in the black list of the push task;
and the second processing module is used for increasing the times of the white list if the identification of the user is in the black list of the push task.
In other embodiments of the present invention, the first determining module is configured to determine that the feedback information is positive feedback information if the feedback information indicates that the user responds to the push task; the first processing module is used for increasing the number of times of the white list if the identification of the user is in the white list of the push task; a second processing module, configured to reduce the number of times of the blacklist if the identifier of the user is in the blacklist of the push task and the number of times of the identifier of the user is in the blacklist of the push task is greater than a minimum threshold; and if the number of times that the user identifier is in the blacklist of the push task is the lowest threshold value, placing the user identifier in the white list of the push task.
In other embodiments of the present invention, the second determining unit includes an obtaining module and a second determining module, wherein:
the acquisition module is used for acquiring a user tag of the user according to the user identification, wherein the user tag is generated by behavior data of the user;
the second determining module is configured to determine a tag of the push task according to the identifier of the push task;
and if the user label is matched with the label of the pushing task, determining that the association index meets the preset first condition, and pushing the pushing task to the client.
Wherein the determining the tag of the push task according to the identifier of the push task includes: and searching a preset association list according to the identifier of the push task to obtain the push task.
In other embodiments of the present invention, the obtaining module is configured to search a local cache for a tag that is concerned by the user according to the identifier of the user; and if the label of the pushing task is matched with the label concerned by the user, determining that the association index meets the preset first condition, and pushing the pushing task to the client.
In other embodiments of the present invention, the obtaining module is configured to send a user tag request to the client, where the tag request is used to request a user tag; and receiving a user tag response sent by the client, wherein the user tag response carries a user tag. Correspondingly, referring to fig. 4B, the client located on the terminal includes a second receiving unit 415, a carrying unit 416, and a second sending unit 417, where the second receiving unit 415 is configured to receive a user tag request sent by the server, and the user tag request is used to request a user tag; a carrying unit 416, configured to respond to the user tag request, and carry the user tag whose weight meets a preset second condition in the user tag response; a second sending unit 417, configured to send the user tag response to the server.
In other embodiments of the present invention, referring to fig. 4B, the client located on the terminal further includes a second detecting unit 411, a fourth determining unit 412, a fifth determining unit 413, and a storage unit 414, where:
a second detecting unit 411, configured to detect a network behavior of the user using the terminal, and perform keyword extraction on an access object of the network behavior;
a fourth determining unit 412, configured to use the keyword as a user tag of the user if the keyword is in the preset tag library, where the preset tag library is configured manually;
a fifth determining unit 413, configured to determine a corresponding weight for the user tag;
a storage unit 414, configured to store the user tag of the user according to a preset storage structure, where the storage structure at least includes the weight and the user tag.
In other embodiments of the present invention, the apparatus further includes a third determining unit and a establishing unit, wherein: the third determining unit is configured to determine, according to the attribute of the push task, a tag of the push task from a preset tag library; or receiving configuration operation on the push task, and determining a label of the push task for the push task according to the configuration operation; the establishing unit is used for establishing an association list between the identification of the push task and the label of the push task;
correspondingly, the second determining module is configured to search a preset association list according to the identifier of the push task to obtain the push task.
In other embodiments of the present invention, the third determining unit includes a third determining module and a fourth determining module, wherein: the third determining module is configured to determine a keyword of the push task according to the content of the push task; the fourth determining module is configured to determine the keyword as a tag of the push task if the keyword is in the preset tag library, where the preset tag library is configured manually.
The above description of the apparatus embodiments, similar to the above description of the method embodiments, has similar beneficial effects as the method embodiments. For technical details not disclosed in the embodiments of the apparatus according to the invention, reference is made to the description of the embodiments of the method according to the invention for understanding.
Based on the foregoing embodiments, embodiments of the present invention provide a device for generating a user tag, where each unit included in the device may be implemented by a processor in a terminal device, such as a computer or a personal computer, or may be implemented by a logic circuit; in the course of the embodiment, the processor may be a CPU, MPU, DSP, FPGA, or the like. The device also includes:
the second detection unit is used for detecting the network behavior of the user using the terminal and extracting keywords of an access object of the network behavior;
a fourth determining unit, configured to take the keyword as a user tag of the user if the keyword is in the preset tag library, where the preset tag library is configured manually;
a fifth determining unit, configured to determine a corresponding weight for the user tag;
a storage unit, configured to store a user tag of the user according to a preset storage structure, where the storage structure at least includes the weight and the user tag;
and the first sending unit is used for sending the user tags with the weights meeting the preset second condition to the server.
In other embodiments of the present invention, the apparatus further comprises: a second receiving unit, configured to receive a user tag request sent by the server, where the user tag request is used to request a user tag; the carrying unit is used for responding to the user tag request and carrying the user tag with the weight meeting a preset second condition in the user tag response; and the second sending unit is used for sending the user tag response to the server.
In other embodiments of the present invention, the first storage structure further includes a latest update time of the user tag, and the apparatus further includes: an updating unit, configured to update the weights in the storage structure according to weight (new) ═ weight (old) - (current time-update) × X + Y; wherein, X is a time attenuation coefficient, Y is a weight number added once, uptime represents the latest updating time, weight (new) represents the current weight, weight (old) represents the previous weight, and if weight (old) - (current time-uptime) X is less than 0, weight is directly set to 1.
The above description of the apparatus embodiments, similar to the above description of the method embodiments, has similar beneficial effects as the method embodiments. For technical details not disclosed in the embodiments of the apparatus according to the invention, reference is made to the description of the embodiments of the method according to the invention for understanding.
In the embodiment of the present invention, if the pushing method or the user tag generation method is implemented in the form of a software functional module and sold or used as an independent product, the pushing method or the user tag generation method may also be stored in a computer-readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or a part contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, or an optical disk, and various media capable of storing program codes. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.
Accordingly, an embodiment of the present invention provides a server, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the push method described above when executing the program. Accordingly, an embodiment of the present invention provides a terminal, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the above-mentioned user tag generation method. Accordingly, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the above-mentioned push method or the above-mentioned user tag generation method. The above description of the server, terminal and storage medium embodiments is similar to the description of the method embodiments described above, with similar beneficial effects as the method embodiments.
In the implementation process, when a server or a terminal is implemented by using a computing device, fig. 5 is a schematic diagram of a hardware entity of the computing device in the embodiment of the present invention, where the hardware entity of the computing device 500 includes: a processor 501, a communication interface 502, an input module 503, a display module 504, and a memory 505, wherein
The processor 501 generally controls the overall operation of the computing device 500. For example, the input module 503 may be implemented as a touch screen, and output user operation data representing operation characteristics (including a touch point position, a touch point number, and a trigger pressure) of the touch screen to the processor 501, and the processor 501 may parse the user operation data to determine a function triggered by a user in the display interface, and generate display data corresponding to the triggered function, so that the display module 504 loads a page corresponding to the triggered function.
The communication interface 502 may enable the computing device to communicate with other terminals or servers over a network.
The input module 503 may be configured to receive input character information and generate signal inputs related to user settings and function controls. The input module may include a touch surface, which may collect a touch operation by a user (e.g., a user's operation on or near the touch surface using a finger, a stylus, or any other suitable object or attachment), acquire a signal from the touch operation, convert the signal into touch coordinates, send the touch coordinates to the processor 501 for processing, and receive and execute a command from the processor 501.
The display module 504 may be configured to display the functions performed by the processor 501 and related information.
The Memory 505 is configured to store instructions and applications executable by the processor 501, and may also buffer data (e.g., image data, audio data, voice communication data, and video communication data) to be processed or already processed by the processor 501 and modules in the computing device 500, and may be implemented by a FLASH Memory (FLASH) or a Random Access Memory 505 (RAM).
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present invention, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention. The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units; can be located in one place or distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment. In addition, all the functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
Those of ordinary skill in the art will understand that: all or part of the steps for realizing the method embodiments can be completed by hardware related to program instructions, the program can be stored in a computer readable storage medium, and the program executes the steps comprising the method embodiments when executed; and the aforementioned storage medium includes: a removable storage device, a ROM, a magnetic or optical disk, or other various media that can store program code.
Alternatively, the integrated unit of the present invention may be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as a separate product. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or a part contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a removable storage device, a ROM, a magnetic or optical disk, or other various media that can store program code.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (11)
1. A push method, the method comprising:
when detecting that connection is established with a client of a user, acquiring an identifier of the user;
determining the weight corresponding to the user identifier according to the user identifier, wherein the weight corresponding to the user identifier changes along with time, and when the weight corresponding to the user identifier changes to a zero value, deleting the user identifier;
determining an identifier of a current push task;
determining a correlation index between a user tag of the user and a tag of the push task according to the identifier of the user and the identifier of the push task, wherein the user tag is generated by behavior data of the user;
if the association index meets a preset first condition, pushing the pushing task to the client;
receiving feedback information of the user on the pushing task, which is sent by the client;
when the feedback information is positive feedback information, generating a white list of the pushing task according to the identification of the user, and when the feedback information is negative feedback information, generating a black list of the pushing task according to the identification of the user;
adjusting the times of the user identification and the push task identification appearing in the blacklist and the white list of the push task according to the feedback information, and
and when the number of times that the user identification appears in the blacklist of the push task is greater than a quantity threshold value, the push task is not pushed to the client.
2. The method of claim 1, wherein the preset first condition comprises less than a preset number of times that the user's identity and the push task's identity appear in the push task's blacklist; if the feedback information is negative feedback information, adjusting the times of the user identifier and the push task identifier appearing in the blacklist and the whitelist of the push task according to the feedback information, including:
if the feedback information indicates that the user closes the push task or does not respond to the push task, determining the feedback information as the negative feedback information;
if the user identifier is in the white list of the push task and the number of times that the user identifier appears in the white list of the push task is greater than a minimum threshold value, reducing the number of times that the user identifier appears in the white list of the push task; if the times that the user identification appears in the white list of the push task is the lowest threshold value, placing the user identification in the black list of the push task;
and if the user identification is in the blacklist of the push task, increasing the times of the user identification appearing in the white list of the push task.
3. The method according to any one of claims 1 to 2, wherein the determining an association index between the user tag of the user and the tag of the push task according to the user identifier and the push task identifier, and if the association index satisfies a preset first condition, pushing the push task to the client includes:
acquiring a user tag of the user according to the user identification, wherein the user tag is generated by behavior data of the user;
determining a label of the push task according to the identification of the push task;
and if the user label is matched with the label of the pushing task, determining that the association index meets the preset first condition, and pushing the pushing task to the client.
4. The method of claim 3, wherein the obtaining the user tag of the user according to the user identifier comprises: searching a label concerned by the user in a local cache according to the identification of the user;
and if the label of the pushing task is matched with the label concerned by the user, determining that the association index meets the preset first condition, and pushing the pushing task to the client.
5. The method of claim 3, wherein the obtaining the user tag of the user according to the user identifier comprises:
sending a user tag request to the client, wherein the tag request is used for requesting a user tag;
and receiving a user tag response sent by the client, wherein the user tag response carries a user tag.
6. The method of claim 3, further comprising:
determining a label of the push task from a preset label library for the push task according to the attribute of the push task; or receiving configuration operation on the push task, and determining a label of the push task for the push task according to the configuration operation;
establishing an association list between the identification of the push task and the label of the push task;
the determining the tag of the push task according to the identifier of the push task includes: and searching a preset association list according to the identifier of the push task to obtain the push task.
7. The method according to claim 6, wherein determining the tag of the push task from a preset tag library for the push task according to the attribute of the push task comprises:
determining keywords of the push task according to the content of the push task;
and if the keyword is in the preset tag library, taking the keyword as a tag of the pushing task, wherein the preset tag library is configured manually.
8. A server comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the push method of any of the preceding claims 1 to 7 when executing the program.
9. A pushing device, the device comprising:
the first detection unit is used for acquiring the identification of a user when detecting that the connection is established with the client of the user; determining a weight corresponding to the user identifier according to the user identifier, wherein the weight corresponding to the user identifier changes with time, and when the weight corresponding to the user identifier changes to a zero value, deleting the user identifier;
the first determining unit is used for determining the identifier of the current push task;
a second determining unit, configured to determine, according to the identifier of the user and the identifier of the push task, an association index between a user tag of the user and a tag of the push task, where the user tag is generated by behavior data of the user;
the pushing unit is used for pushing the pushing task to the client if the association index meets a preset first condition;
the first receiving unit is used for receiving feedback information of the user on the pushing task, which is sent by the client; when the feedback information is positive feedback information, generating a white list of the pushing task according to the identification of the user, and when the feedback information is negative feedback information, generating a black list of the pushing task according to the identification of the user;
and the modifying unit is used for adjusting the times of the user identifier and the push task identifier appearing in the blacklist and the white list of the push task according to the feedback information, and when the times of the user identifier appearing in the blacklist of the push task are larger than a quantity threshold value, the push task is not pushed to the client.
10. A computer-readable storage medium having computer-executable instructions stored thereon which, when executed by a processor, perform the method steps of any of claims 1 to 7.
11. A computer device comprising a memory, a processor and computer-executable instructions stored on the memory and executable on the processor, wherein the processor implements the method steps of any one of claims 1 to 7 when executing the computer-executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710329231.0A CN108881339B (en) | 2017-05-11 | 2017-05-11 | Push method, user tag generation method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710329231.0A CN108881339B (en) | 2017-05-11 | 2017-05-11 | Push method, user tag generation method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108881339A CN108881339A (en) | 2018-11-23 |
| CN108881339B true CN108881339B (en) | 2022-05-13 |
Family
ID=64319446
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710329231.0A Active CN108881339B (en) | 2017-05-11 | 2017-05-11 | Push method, user tag generation method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108881339B (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110035108B (en) * | 2018-12-26 | 2022-01-28 | 创新先进技术有限公司 | Information pushing method and system |
| CN111402375B (en) * | 2019-01-03 | 2023-09-08 | 百度在线网络技术（北京）有限公司 | Shutter effect forming method and device and rendering engine |
| CN110287372B (en) * | 2019-06-26 | 2021-06-01 | 广州市百果园信息技术有限公司 | Label determining method for negative feedback, video recommending method and device thereof |
| CN110708360A (en) * | 2019-09-17 | 2020-01-17 | Oppo广东移动通信有限公司 | Information processing method and system and electronic equipment |
| CN111083211B (en) * | 2019-12-09 | 2023-08-11 | 广州探途网络技术有限公司 | User touch method and system based on big data platform |
| CN111538900B (en) * | 2020-03-30 | 2021-07-20 | 平安科技（深圳）有限公司 | Information recommendation method and related equipment |
| CN111489206A (en) * | 2020-04-16 | 2020-08-04 | 北京雷石天地电子技术有限公司 | Information pushing method, information pushing device and readable storage medium |
| CN112583920B (en) * | 2020-12-14 | 2023-12-22 | 维沃移动通信有限公司 | Push method, push device, electronic equipment and storage medium |
| CN112968928A (en) * | 2021-01-28 | 2021-06-15 | 支付宝(杭州)信息技术有限公司 | Information processing method and device |
| CN112800340A (en) * | 2021-04-14 | 2021-05-14 | 北京轻松筹信息技术有限公司 | Task pushing method and device, electronic equipment and storage medium |
| CN113905090B (en) * | 2021-09-16 | 2023-07-07 | 平安科技（深圳）有限公司 | Message pushing method, device, server, electronic equipment and storage medium |
| CN115314459A (en) * | 2022-08-12 | 2022-11-08 | 中国平安财产保险股份有限公司 | Information push management method and device, computer equipment and storage medium |
| CN115511524B (en) * | 2022-09-26 | 2023-09-26 | 陕西励爱互联网科技有限公司 | Advertisement pushing method, system and cloud platform |
| CN116055551A (en) * | 2022-11-18 | 2023-05-02 | 北京奇艺世纪科技有限公司 | Information pushing method, device and system, electronic equipment and storage medium |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101262497A (en) * | 2008-04-21 | 2008-09-10 | 深圳市迅雷网络技术有限公司 | A content push method, system and device |
| CN101847160A (en) * | 2010-05-19 | 2010-09-29 | 深圳市五巨科技有限公司 | Method and device for pushing personalized pages to mobile terminal |
| CN102790727A (en) * | 2011-05-19 | 2012-11-21 | 腾讯科技（深圳）有限公司 | Method and system for dynamically pushing personal labels of users |
| WO2014012477A1 (en) * | 2012-07-16 | 2014-01-23 | 腾讯科技（深圳）有限公司 | Network information pushing system and method |
| CN103840950A (en) * | 2014-02-27 | 2014-06-04 | 广东亿迅科技有限公司 | Information pushing method and system |
| CN104657428A (en) * | 2015-01-26 | 2015-05-27 | 暨南大学 | Non-perceivable internet advertisement push method and device |
| CN106227874A (en) * | 2016-07-29 | 2016-12-14 | 中国传媒大学 | A kind of mobile news client based on UCL |
| CN106462865A (en) * | 2014-03-13 | 2017-02-22 | 株式会社实虚螺旋 | Tag management system, tag management method, information provision system, and information provision method, as well as devices and tag used therefor |
| CN106469181A (en) * | 2015-08-21 | 2017-03-01 | 方正国际软件(北京)有限公司 | A kind of user behavior pattern analysis method and device |
| CN106506521A (en) * | 2016-11-28 | 2017-03-15 | 腾讯科技（深圳）有限公司 | resource access control method and device |
| CN106649522A (en) * | 2016-10-18 | 2017-05-10 | 江西博瑞彤芸科技有限公司 | User information acquisition method based on push message |
| CN107301565A (en) * | 2017-06-12 | 2017-10-27 | 北京望远传媒有限公司 | The method for pushing and device of a kind of screen message |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7242988B1 (en) * | 1991-12-23 | 2007-07-10 | Linda Irene Hoffberg | Adaptive pattern recognition based controller apparatus and method and human-factored interface therefore |
| WO2008035044A2 (en) * | 2006-09-18 | 2008-03-27 | Yann Emmanuel Motte | Methods and apparatus for selection of information and web page generation |
| US9246932B2 (en) * | 2010-07-19 | 2016-01-26 | Sitelock, Llc | Selective website vulnerability and infection testing |
| US20140279190A1 (en) * | 2013-03-14 | 2014-09-18 | SimpleRelevance Inc. | Recommended content generation and distribution |
| CN104184746B (en) * | 2014-09-12 | 2019-12-31 | 网神信息技术（北京）股份有限公司 | Method and device for processing data by gateway |
| CN104899315A (en) * | 2015-06-17 | 2015-09-09 | 百度在线网络技术（北京）有限公司 | Method and device for pushing user information |
| CN105868254A (en) * | 2015-12-25 | 2016-08-17 | 乐视网信息技术（北京）股份有限公司 | Information recommendation method and apparatus |
| CN106294787A (en) * | 2016-08-12 | 2017-01-04 | 北京金山安全软件有限公司 | Information pushing method and device and electronic equipment |
-
2017
- 2017-05-11 CN CN201710329231.0A patent/CN108881339B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101262497A (en) * | 2008-04-21 | 2008-09-10 | 深圳市迅雷网络技术有限公司 | A content push method, system and device |
| CN101847160A (en) * | 2010-05-19 | 2010-09-29 | 深圳市五巨科技有限公司 | Method and device for pushing personalized pages to mobile terminal |
| CN102790727A (en) * | 2011-05-19 | 2012-11-21 | 腾讯科技（深圳）有限公司 | Method and system for dynamically pushing personal labels of users |
| WO2014012477A1 (en) * | 2012-07-16 | 2014-01-23 | 腾讯科技（深圳）有限公司 | Network information pushing system and method |
| CN103840950A (en) * | 2014-02-27 | 2014-06-04 | 广东亿迅科技有限公司 | Information pushing method and system |
| CN106462865A (en) * | 2014-03-13 | 2017-02-22 | 株式会社实虚螺旋 | Tag management system, tag management method, information provision system, and information provision method, as well as devices and tag used therefor |
| CN104657428A (en) * | 2015-01-26 | 2015-05-27 | 暨南大学 | Non-perceivable internet advertisement push method and device |
| CN106469181A (en) * | 2015-08-21 | 2017-03-01 | 方正国际软件(北京)有限公司 | A kind of user behavior pattern analysis method and device |
| CN106227874A (en) * | 2016-07-29 | 2016-12-14 | 中国传媒大学 | A kind of mobile news client based on UCL |
| CN106649522A (en) * | 2016-10-18 | 2017-05-10 | 江西博瑞彤芸科技有限公司 | User information acquisition method based on push message |
| CN106506521A (en) * | 2016-11-28 | 2017-03-15 | 腾讯科技（深圳）有限公司 | resource access control method and device |
| CN107301565A (en) * | 2017-06-12 | 2017-10-27 | 北京望远传媒有限公司 | The method for pushing and device of a kind of screen message |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108881339A (en) | 2018-11-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108881339B (en) | Push method, user tag generation method, device and equipment | |
| US11108807B2 (en) | Performing rule-based actions for newly observed domain names | |
| RU2522103C2 (en) | Update notification method and browser | |
| CN106357517B (en) | Directional label generation method and device | |
| CN110046299B (en) | Computerized system and method for automatically performing an implicit message search | |
| CN111740896B (en) | Content sharing control method and device, electronic equipment and storage medium | |
| US9317612B1 (en) | System and method for managing multiple content feeds | |
| CN104850546B (en) | Display method and system of mobile media information | |
| KR102504075B1 (en) | Matching and attributes of user device events | |
| CN103428076A (en) | Method and device for transmitting information to multi-type terminals or applications | |
| CN103840950A (en) | Information pushing method and system | |
| EP2817738B1 (en) | Predictive service access | |
| CN102541853A (en) | Method and device which are capable of obtaining application information by utilizing browser address bar | |
| CN105577815A (en) | Delivery method and delivery system of reading precise delivery system and processor | |
| CN104881774A (en) | Method and apparatus for automatically establishing schedule | |
| CN107515869B (en) | Searching method and device and searching device | |
| CN111078986A (en) | Data retrieval method, device and computer readable storage medium | |
| CN109471974A (en) | Filter method, apparatus, electronic equipment and the storage medium of third party's web advertisement | |
| KR20130026558A (en) | System and providing method for integration of reply comment | |
| KR100840019B1 (en) | Method and system for providing advertisements using schedule information | |
| JP2008108105A (en) | Information providing device, information providing method and information providing program | |
| CN112486796B (en) | Method and device for collecting information of vehicle-mounted intelligent terminal | |
| KR20190098810A (en) | Method and server for interactive message service | |
| CN114816180A (en) | Content browsing guiding method and device, electronic equipment and storage medium | |
| CN105450510A (en) | Friend management method, device and server for social network platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20221117 Address after: 1402, Floor 14, Block A, Haina Baichuan Headquarters Building, No. 6, Baoxing Road, Haibin Community, Xin'an Street, Bao'an District, Shenzhen, Guangdong 518133 Patentee after: Shenzhen Yayue Technology Co.,Ltd. Address before: 518000 Tencent Building, No. 1 High-tech Zone, Nanshan District, Shenzhen City, Guangdong Province, 35 Floors Patentee before: TENCENT TECHNOLOGY (SHENZHEN) Co.,Ltd. |