CN107733968B - Application information pushing method and device, computer equipment and storage medium - Google Patents
Application information pushing method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN107733968B CN107733968B CN201710608519.1A CN201710608519A CN107733968B CN 107733968 B CN107733968 B CN 107733968B CN 201710608519 A CN201710608519 A CN 201710608519A CN 107733968 B CN107733968 B CN 107733968B
- Authority
- CN
- China
- Prior art keywords
- push
- pushing
- user account
- application
- task
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention relates to an application information pushing method, an application information pushing device, computer equipment and a storage medium, wherein the method comprises the following steps: acquiring an application pushing task; extracting a push information type and a user account in the application push task; inquiring historical push records according to the extracted push information types and the user accounts; counting the pushed times corresponding to each user account according to the inquired historical pushing records; screening and counting user accounts with the pushed times smaller than the preset pushed times from the extracted user accounts; and executing the application pushing task according to the screened user account. The application information pushing method, the application information pushing device, the computer equipment and the storage medium avoid the situation that the number of the users of the application is reduced due to the fact that the screened user accounts frequently receive the pushing messages of the same pushing information type and the application is unloaded.
Description
Technical Field
The present invention relates to the field of information processing technologies, and in particular, to an application information pushing method and apparatus, a computer device, and a storage medium.
Background
With the rapid development of internet technology and computer technology, more and more applications are developed, and the developed applications are installed in terminals. Various application information can be pushed to a terminal provided with an application program through the Internet, so that a user can acquire related application information in time through the terminal.
With the increasing demand of pushing application information, the amount of tasks for pushing application information through the internet is increased, and the number of applications received by a user is increased. Too frequent pushing of the application messages may cause the user to uninstall the application with too frequent pushing, resulting in a reduction in the number of users corresponding to the application.
Disclosure of Invention
Based on this, it is necessary to provide an application information pushing method, apparatus, computer device, and storage medium for the problem of a reduction in the number of users of an application.
An application information pushing method, the method comprising:
acquiring an application pushing task;
extracting a push information type and a user account in the application push task;
inquiring historical push records according to the extracted push information types and the user accounts;
counting the pushed times corresponding to each user account according to the inquired historical pushing records;
screening and counting user accounts with the pushed times smaller than the preset pushed times from the extracted user accounts;
and executing the application pushing task according to the screened user account.
An application information pushing apparatus, the apparatus comprising:
the push task acquisition module is used for acquiring an application push task;
the push task analysis module is used for extracting a push information type and a user account in the application push task;
the pushing record query module is used for querying a historical pushing record according to the extracted pushing information type and the user account;
the pushing times counting module is used for counting the pushing times corresponding to the user accounts according to the inquired historical pushing records;
the pushing times comparing module is used for screening and counting the user accounts with the pushing times smaller than the preset pushing times from the extracted user accounts;
and the pushing task execution module is used for executing the application pushing task according to the screened user account.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
acquiring an application pushing task;
extracting a push information type and a user account in the application push task;
inquiring historical push records according to the extracted push information types and the user accounts;
counting the pushed times corresponding to each user account according to the inquired historical pushing records;
screening and counting user accounts with the pushed times smaller than the preset pushed times from the extracted user accounts;
and executing the application pushing task according to the screened user account.
One or more storage media storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of:
acquiring an application pushing task;
extracting a push information type and a user account in the application push task;
inquiring historical push records according to the extracted push information types and the user accounts;
counting the pushed times corresponding to each user account according to the inquired historical pushing records;
screening and counting user accounts with the pushed times smaller than the preset pushed times from the extracted user accounts;
and executing the application pushing task according to the screened user account.
According to the application information pushing method, the application information pushing device, the computer equipment and the storage medium, the pushing information type and the user account in the application pushing task are extracted, the historical pushing records corresponding to the extracted pushing information type and the user account are inquired, the pushing times corresponding to the user accounts are counted according to the historical pushing records, the user accounts with the pushing times smaller than the preset pushing times are screened and counted from the extracted user accounts, and the application pushing task is executed according to the screened user accounts. The user accounts are screened according to the pushing times, the screened users corresponding to the user accounts can be guaranteed to be users who receive the pushing information of the extracted pushing information type less than the preset pushing times, the screened users corresponding to the user accounts can be guaranteed not to frequently receive the pushing information of the same pushing information type, therefore, the situation that the screened user accounts unload the application due to the fact that the screened user accounts frequently receive the pushing information of the same pushing information type is avoided, and the situation that the number of the users of the application is reduced is avoided.
Drawings
FIG. 1 is a diagram of an application environment in which a push method for information is applied in one embodiment;
FIG. 2 is a block diagram illustrating an exemplary server in the application information pushing system;
FIG. 3 is a flowchart illustrating an application information pushing method according to an embodiment;
FIG. 4 is a flowchart illustrating the steps of detecting a type of push information in one embodiment;
FIG. 5 is a flowchart illustrating steps of generating push disturb alert messages in one embodiment;
FIG. 6 is a flowchart illustrating steps for updating a history push record in one embodiment;
FIG. 7 is a block diagram showing an exemplary embodiment of an application information pushing apparatus;
FIG. 8 is a block diagram showing the construction of an application information pushing apparatus according to another embodiment;
fig. 9 is a block diagram showing a configuration of an application information pushing apparatus according to still another embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention 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 invention and are not intended to limit the invention.
Fig. 1 is a diagram of an application environment in which the information push method is applied in one embodiment. Referring to fig. 1, the application information push method is applied to an application information push system. The application information pushing system comprises a terminal 110 and a server 120, wherein the terminal 110 is connected with the server 120 through a network. The terminal 110 may be a fixed terminal, which may specifically be at least one of a printer, a scanner, and a monitor, or a mobile terminal, which may specifically be at least one of a tablet, a smartphone, a personal data assistant, and a digital camera.
Fig. 2 is a schematic diagram illustrating an internal structure of the server 120 in the application information pushing system in fig. 1 according to an embodiment. As shown in fig. 2, the server 120 includes a processor, a nonvolatile storage medium, an internal memory, and a network interface, which are connected through a system bus. The processor of the server 120 is used to provide computing and control capabilities, to support the operation of the entire server 120, the memory is used to store data, code instructions, etc., and the network interface is used to communicate with the terminal 110 over a network. The memory stores at least one computer executable instruction, which can be executed by the processor to implement the application information pushing method provided in the embodiment of the present application and applied to the server 120. The Memory may include a non-volatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a Random Access Memory (RAM). For example, in one embodiment, the memory includes a non-volatile storage medium and an internal memory; the nonvolatile storage medium stores an operating system, a database and computer-executable instructions, wherein the database stores historical push records corresponding to user accounts, and the computer-executable instructions can be executed by the processor to realize the application information push method; the internal memory provides a cached execution environment for the operating system and computer-executable instructions in the non-volatile storage medium.
As shown in fig. 3, in an embodiment, an application information pushing method is provided, which is exemplified by applying the method to the server 120 in fig. 1, and the method specifically includes the following steps:
s302, acquiring an application pushing task.
Specifically, the terminal 110 obtains a task manager account input by a task manager, generates a task page pushing request according to the obtained task manager account, and sends the task page pushing request to the server 120.
The server 120 receives a push task page request sent by the terminal 110, parses the push task page request, extracts a task manager account in the push task page request through parsing, and verifies whether the extracted task manager account has a right to access the push task page. After verifying that the extracted task administrator account has the right to access the push task page, the server 120 obtains data of the push task page, and returns the obtained data of the push task page to the terminal 110 corresponding to the request of the push task page.
The terminal 110 receives the push task page data returned by the server 120, and displays the push task page according to the push task page data. The terminal 110 detects a push task creation instruction triggered by a task manager on a push task page. The terminal 110 acquires push information and a user account input by a task administrator in a push task page according to a push task creation instruction, generates an application push task according to the acquired push information and the user account, and sends the generated application push task to the server 120. The server 120 receives the application push task transmitted by the terminal 110.
S304, extracting the push information type and the user account in the application push task.
Specifically, the server 120 parses the application push task, and extracts the push information type and the user account in the application push task through parsing. The push information type is a type to which push information in the application push task belongs, and the push information type comprises at least one of a marketing type, a service type and a notification type. The user account is a target user account in the application task.
S306, inquiring historical push records according to the extracted push information types and the user accounts.
Specifically, the database of the server 120 stores a history push record corresponding to the user account. The history push record comprises the type of push information, the user account and the push time, and can also comprise the push times. The server 120 first queries a historical push record corresponding to the extracted user account from the historical push records in the database, and then queries a historical push record corresponding to the extracted push information type from the historical push records corresponding to the extracted user account.
In one embodiment, the server 120 may further query the history push records in the history push records of the database, where the history push records correspond to the extracted push information types, and then query the history push records in the history push records corresponding to the extracted push information types.
And S308, counting the pushed times corresponding to each user account according to the inquired historical pushing records.
Specifically, the server 120 extracts the historical push records corresponding to the user accounts from the queried historical push records, and counts the number of times of pushing corresponding to each user account according to the historical push records corresponding to each user account.
And S310, screening and counting the user accounts with the pushed times smaller than the preset pushed times from the extracted user accounts.
Specifically, the server 120 compares the pushed times corresponding to each user account in the extracted user accounts with preset pushed times, determines the user account with the pushed times smaller than the preset pushed times through comparison, and screens out the determined user account from the extracted user accounts.
And S312, executing an application pushing task according to the screened user account.
Specifically, the server 120 extracts the push information in the application push task, and creates an application push subtask according to the extracted push information and each of the screened user accounts. And the created application pushing subtasks correspond to each user account in the screened user accounts one by one.
In one embodiment, the server 120 extracts the push information in the application push task, creates an application push subtask according to each user account in the screened user accounts and the extracted push information, and adds the created application push subtask to the task queue. The server 120 reads the application push subtask from the task queue and executes the read application push subtask.
In an embodiment, the application information pushing method specifically further includes the following steps: acquiring a current time point; comparing the current time point with a preset time point; and if the current time point is the same as the preset time point, deleting the historical push records corresponding to the user accounts.
For example, the preset time point is set to 0 point every day, and when the server 120 detects that the current time is 0 point, the historical push records corresponding to each user account in the database are deleted. The server 120 can be ensured to screen the user account according to the historical push record in one day, and the accuracy of screening the user account is improved.
In this embodiment, the push information type and the user account in the application push task are extracted, a history push record corresponding to the extracted push information type and the extracted user account is queried, push times corresponding to the user accounts are counted according to the history record, the user accounts with the push times smaller than a preset push time are screened and counted from the extracted user accounts, and the application push task is executed according to the screened user accounts. The user accounts are screened according to the pushing times, the screened users corresponding to the user accounts can be guaranteed to be users who receive the pushing information of the extracted pushing information type less than the preset pushing times, the screened users corresponding to the user accounts can be guaranteed not to frequently receive the pushing information of the same pushing information type, therefore, the situation that the screened user accounts unload the application due to the fact that the screened user accounts frequently receive the pushing information of the same pushing information type is avoided, and the situation that the number of the users of the application is reduced is avoided.
As shown in fig. 4, in an embodiment, after S304, a step of detecting a type of the push information is further specifically included, where the step specifically includes the following:
s402, acquiring a push type restriction list.
Specifically, the database of the server 120 stores a push type restriction list. The push type limitation list is used for identifying whether push information in the application push task is limited by certain push. The push type limitation list comprises push information types, and the push information types in the push type limitation list are the push information types of the limited push information. The server 120 retrieves the push type restriction list from the database.
S404, the extracted push information type is inquired in the push type limit list.
Specifically, after acquiring the push type restriction list, the server 120 queries the extracted push information type in the push type restriction list, and if the extracted push information type is queried, determines that the application push task is an application push task that is not restricted by push; if not, the application pushing task is judged to be the application pushing task limited by pushing.
And S406, if the extracted push information type is not inquired in the push type limit list, judging that the application push task is not limited by push, and executing the application push task according to the extracted user account.
Specifically, when the push type limitation list does not query the extracted push information type, the server 120 determines that the application push task is an application push task that is not limited by push. The server 120 analyzes the application push task, extracts push information in the application push task through analysis, creates an application push subtask according to each user account in the extracted user accounts and the extracted push information, and adds the created application push subtask to the task queue. The server 120 reads the application push subtask from the task queue and executes the read application push subtask.
In one embodiment, when the push type restriction list queries the extracted push information type, the server 120 determines that the application push task is a push-restricted application push task, and needs to be restricted according to the history push record. The server 120 queries a historical pushing record according to the extracted pushing information type and the user account, counts the pushing times corresponding to each user account according to the queried historical pushing record, screens the user accounts with the pushing times smaller than the preset pushing times from the extracted user accounts, and executes an application pushing task according to the screened user accounts.
In this embodiment, when the push information type of the application push task is queried in the push type restriction list, the application push task corresponding to the queried push information type is restricted. And the application push task to be controlled is set through the push information type list, so that the control efficiency of the application push task is improved. The pushing times of the application pushing tasks corresponding to the pushing information types in the pushing type limiting list to the same user account are controlled, and the situation that the user account receives the pushing information corresponding to the same pushing information type for multiple times is avoided.
As shown in fig. 5, in an embodiment, after S312, a step of generating push disturbing alert information is further specifically included, where the step specifically includes the following steps:
and S502, acquiring the remaining screened user accounts from the extracted user accounts.
Specifically, the server 120 obtains the remaining user accounts from the extracted user accounts after screening out the user accounts whose pushing times are less than the preset pushing times.
In one embodiment, the server 120 screens out the user accounts with the pushed times greater than or equal to the preset pushed times from the extracted user accounts.
And S504, generating push disturbance reminding information according to the acquired user account.
Specifically, the server 120 extracts the pushed times corresponding to the acquired user account, and generates the push disturbance prompting information according to the acquired user account and the pushed times corresponding to the acquired user account. For example, the push disturbance reminder message is "the user account a has been pushed N times; the user account B has been pushed M times ".
S506, the push disturbance reminding information is sent to the terminal logged in by the task manager account.
Specifically, the server 120 queries the terminal 120 logged in with the task administrator account, and sends the push disturbance reminder information to the queried terminal 110. The terminal 110 displays the push disturbance reminder information on a push task page.
And S508, receiving a forced push instruction returned by the terminal logged in by the task administrator account according to the push disturbance reminding information.
Specifically, a forced push button is arranged in a push task page of the terminal 110 displaying the push disturbing reminding information. After viewing the push disturbance prompt message, the push administrator clicks the forced push button through the input device of the terminal 110 when deciding to force the push. When the terminal 110 detects that the forced push button is clicked, a forced push instruction is triggered. The terminal 110 sends a forced push instruction to the server 120.
In one embodiment, a abandon push button is arranged in a push task page of the terminal displaying the push disturbance reminding information. After checking the push disturbing reminding information, the push administrator decides to give up information push to the user account corresponding to the push disturbing reminding information, and then clicks a push giving-up button through an input device of the terminal 110. When the terminal 110 detects that the abandon push button is clicked, the abandon push instruction is triggered, and the terminal 110 sends the triggered abandon push instruction to the server 120. The server 120 gives up information push on the acquired user account according to the giving up push instruction.
And S510, executing an application pushing task by taking the obtained user account as a target user account according to the forced pushing instruction.
Specifically, after receiving the forced push instruction returned by the terminal 110, the server 120 performs application push by using the acquired user account as a target user account of the application push task.
In an embodiment, the server 120 extracts each user account from the acquired user accounts, creates an application push subtask by using each extracted user account as a target user account, and adds the created application push subtask to the task queue. The server 120 may read the application push subtasks from the task queue according to the preset read data, and concurrently execute the read application push subtasks.
In one embodiment, the server 120 extracts the read push information and the user account in the application push subtask, queries a terminal logged in with the extracted user account, and sends the extracted push information to the queried terminal.
In this embodiment, push disturbance reminding information is generated according to the acquired user account, and the push disturbance reminding information is sent to a terminal logged in by a task manager account. Therefore, the task manager is reminded of the fact that pushing disturbance possibly occurs to the user account, and whether information pushing is carried out on the obtained user account or not can be determined according to disturbance reminding information by the task manager.
As shown in fig. 6, in an embodiment, after S510, a step of updating the history push record is further specifically included, where the step specifically includes the following steps:
s602, extracting the user account corresponding to the executed application push task.
Specifically, the server 120 marks the application push task as executed after the application push task is executed. The server 120 parses the executed application push task, and extracts the user account in the executed application push task through parsing.
S604, judging whether the extracted user account is a push limitation account.
Specifically, the database of the server 120 stores the push restriction account. The server 120 queries the extracted user account from the stored push-restricted accounts, and if the extracted user account is queried from the push-restricted accounts, determines that the extracted user account is a push-restricted account; if the extracted user account is not queried in the push limitation account, it is determined that the extracted user account is not the push limitation account, and an application push task of the user account which is not the push limitation account is not recorded.
And S606, if the extracted user account is determined to be the push limiting account, extracting the push information type in the executed application push task.
Specifically, when determining that the extracted user account is a push-restricted account, the server 120 analyzes the executed application push task, and extracts a push information type in the executed application push task through analysis.
And S608, updating the historical push record corresponding to the extracted user account according to the type of the extracted push information.
Specifically, the server 120 queries the extracted user account and the history push record corresponding to the push information type, and updates the pushed times in the queried history push record, for example, adding one to the pushed times in the queried history push record.
In one embodiment, the server 120 obtains the push time of the pushed application push task, and correspondingly stores the obtained push time, the user account extracted from the pushed application push task, and the type of push information as a history push record.
In one embodiment, the application push method specifically further includes: receiving a push limit list configuration instruction sent by a terminal logged in by a task manager account; extracting a user account in a push restriction list configuration instruction; and creating a pushing user restricted list according to the extracted user account.
S604 specifically includes: acquiring a push user restriction list; and judging whether the extracted user account is a push limited account or not according to the push user limited list.
Specifically, the terminal 110 logged in with the task administrator account acquires the user account input by the task administrator and to be configured as the push limitation account, generates a push limitation list configuration instruction according to the acquired account, and sends the push limitation list configuration instruction to the server 120. The server 120 analyzes the push restriction list configuration instruction, extracts the user account in the push restriction list configuration instruction through analysis, and creates a push user restriction list according to the extracted user account. The server 120 obtains the push user restriction list, and determines whether the user account is a push restriction account according to the push user restriction list.
In the embodiment, when the user account in the executed application pushing task is determined to be the pushing limit account, the historical pushing record corresponding to the user account is updated according to the type of the information pushed from the executed application pushing task, so that the accuracy of the historical pushing record is ensured, and the accuracy of screening the user account according to the historical pushing record is improved.
As shown in fig. 7, in an embodiment, an application information pushing apparatus 700 is provided, which specifically includes the following: a push task obtaining module 702, a push task analyzing module 704, a push record querying module 706, a push times counting module 708, a push times comparing module 710, and a push task executing module 712.
A push task obtaining module 702, configured to obtain an application push task.
And the push task analysis module 704 is configured to extract a push information type and a user account in the application push task.
And a push record query module 706, configured to query a historical push record according to the extracted push information type and the user account.
The pushing times counting module 708 is configured to count the pushing times corresponding to each user account according to the queried historical pushing records.
The pushing times comparing module 710 is configured to filter, from the extracted user accounts, user accounts whose pushed times are smaller than a preset pushing time.
And a push task execution module 712, configured to execute an application push task according to the screened user account.
In this embodiment, the push information type and the user account in the application push task are extracted, a history push record corresponding to the extracted push information type and the extracted user account is queried, push times corresponding to the user accounts are counted according to the history record, the user accounts with the push times smaller than a preset push time are screened and counted from the extracted user accounts, and the application push task is executed according to the screened user accounts. The user accounts are screened according to the pushing times, the screened users corresponding to the user accounts can be guaranteed to be users who receive the pushing information of the extracted pushing information type less than the preset pushing times, the screened users corresponding to the user accounts can be guaranteed not to frequently receive the pushing information of the same pushing information type, and therefore the situation that the number of the users of the application is reduced due to the fact that the screened user accounts frequently receive the pushing information of the same pushing information type and the application is unloaded is avoided.
As shown in fig. 8, in an embodiment, the application information pushing apparatus 700 further includes the following contents: a restriction list acquisition module 714 and an information type query module 716.
A restriction list obtaining module 714, configured to obtain the push type restriction list.
An information type query module 716, configured to query the push type restriction list for the extracted push information type.
The push task execution module 712 is further configured to determine that the application push task is an application push task that is not limited by push if the extracted push information type is not queried in the push type limitation list, and execute the application push task according to the extracted user account;
the push record query module 706 is further configured to, if the extracted push information type is queried in the push type limitation list, determine that the application push task is an application push task limited by pushing, and query a historical push record according to the extracted push information type and the user account.
In this embodiment, when the push information type of the application push task is queried in the push type restriction list, the application push task corresponding to the queried push information type is restricted. And the application push task to be controlled is set through the push information type list, so that the control efficiency of the application push task is improved. The pushing times of the application pushing tasks corresponding to the pushing information types in the pushing type limiting list to the same user account are controlled, and the situation that the user account receives the pushing information corresponding to the same pushing information type for multiple times is avoided.
As shown in fig. 9, in an embodiment, the application information pushing apparatus 700 further includes the following contents: the system comprises a user account acquisition module 718, a reminding information generation module 720, a reminding information sending module 722 and a push instruction push module 724.
The user account obtaining module 718 is configured to obtain the remaining user accounts after the screening from the extracted user accounts.
And a reminding information generating module 720, configured to generate push disturbing reminding information according to the obtained user account.
And the reminding information sending module 722 is configured to send the push disturbing reminding information to a terminal logged in with a task manager account.
The push instruction pushing module 724 is configured to receive a forced push instruction returned by the terminal logged in with the task administrator account according to the push disturbance reminding information.
The push task execution module 712 is further configured to execute the application push task by using the obtained user account as the target user account according to the forced push instruction.
In this embodiment, push disturbance reminding information is generated according to the acquired user account, and the push disturbance reminding information is sent to a terminal logged in by a task manager account. Therefore, the task manager is reminded of the fact that pushing disturbance possibly occurs to the user account, and whether information pushing is carried out on the obtained user account or not can be determined according to disturbance reminding information by the task manager.
In one embodiment, the push record query module 706 is further configured to extract a user account corresponding to the executed application push task; judging whether the extracted user account is a push limitation account; if the extracted user account is judged to be a push limiting account, extracting a push information type in the executed application push task; and updating the extracted historical push records corresponding to the user accounts according to the extracted push information types. Judging whether the extracted user account is a push limitation account, including: acquiring a push user restriction list; and judging whether the extracted user account is a push limited account or not according to the push user limited list.
In an embodiment, the application information pushing apparatus 700 further specifically includes a restricted list creating module. The system comprises a limit list creating module, a task manager account login module and a task manager configuration module, wherein the limit list creating module is used for receiving a push limit list configuration instruction sent by a terminal logged in by the task manager account; extracting a user account in a push restriction list configuration instruction; and creating a pushing user restricted list according to the extracted user account.
In the embodiment, when the user account in the executed application pushing task is determined to be the pushing limit account, the historical pushing record corresponding to the user account is updated according to the type of the information pushed from the executed application pushing task, so that the accuracy of the historical pushing record is ensured, and the accuracy of screening the user account according to the historical pushing record is improved.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program: acquiring an application pushing task; extracting a push information type and a user account in an application push task; inquiring historical push records according to the extracted push information types and the user accounts; counting the pushed times corresponding to each user account according to the inquired historical pushing records; screening and counting user accounts with the pushed times smaller than the preset pushed times from the extracted user accounts; and executing the application pushing task according to the screened user account.
In one embodiment, after extracting the push information type and the user account in the application push task, the processor executes the computer program to further implement the following steps: acquiring a push type restriction list; inquiring the extracted push information type in a push type limit list; if the query is not received, judging that the application pushing task is not limited by pushing, and executing the application pushing task according to the extracted user account; and if the query is received, judging that the application pushing task is the application pushing task limited by pushing, and executing the step of querying the historical pushing record according to the extracted pushing information type and the user account.
In one embodiment, after executing the application push task according to the screened user account, the processor executes the computer program to further implement the following steps: obtaining the remaining screened user accounts from the extracted user accounts; generating push disturbance reminding information according to the acquired user account; sending the push disturbance reminding information to a terminal logged in by a task manager account; receiving a forced push instruction returned by a terminal logged in by a task manager account according to the push disturbance reminding information; and executing the application pushing task by taking the obtained user account as a target user account according to the forced pushing instruction.
In an embodiment, after executing an application push task with an acquired user account as a target user account according to a forced push instruction, the processor further implements the following steps when executing a computer program: extracting a user account corresponding to the executed application pushing task; judging whether the extracted user account is a push limitation account; if not, extracting the push information type in the executed application push task; and updating the extracted historical push records corresponding to the user accounts according to the extracted push information types.
In one embodiment, the processor, when executing the computer program, further performs the steps of: receiving a push limit list configuration instruction sent by a terminal logged in by a task manager account; extracting a user account in a push restriction list configuration instruction; and creating a pushing user restricted list according to the extracted user account. Judging whether the extracted user account is a push limitation account, including: acquiring a push user restriction list; and judging whether the extracted user account is a push limited account or not according to the push user limited list.
In this embodiment, the push information type and the user account in the application push task are extracted, a history push record corresponding to the extracted push information type and the extracted user account is queried, push times corresponding to the user accounts are counted according to the history record, the user accounts with the push times smaller than a preset push time are screened and counted from the extracted user accounts, and the application push task is executed according to the screened user accounts. The user accounts are screened according to the pushing times, the screened users corresponding to the user accounts can be guaranteed to be users who receive the pushing information of the extracted pushing information type less than the preset pushing times, the screened users corresponding to the user accounts can be guaranteed not to frequently receive the pushing information of the same pushing information type, and therefore the situation that the number of the users of the application is reduced due to the fact that the screened user accounts frequently receive the pushing information of the same pushing information type and the application is unloaded is avoided.
One or more storage media storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of: acquiring an application pushing task; extracting a push information type and a user account in an application push task; inquiring historical push records according to the extracted push information types and the user accounts; counting the pushed times corresponding to each user account according to the inquired historical pushing records; screening and counting user accounts with the pushed times smaller than the preset pushed times from the extracted user accounts; executing application pushing task according to screened user account
In one embodiment, after extracting the push information type and the user account in the application push task, the processor executes the computer program to further implement the following steps: acquiring a push type restriction list; inquiring the extracted push information type in a push type limit list; if the query is not received, judging that the application pushing task is not limited by pushing, and executing the application pushing task according to the extracted user account; and if the query is received, judging that the application pushing task is the application pushing task limited by pushing, and executing the step of querying the historical pushing record according to the extracted pushing information type and the user account.
In one embodiment, after executing the application push task according to the screened user account, the processor further executes the following steps: obtaining the remaining screened user accounts from the extracted user accounts; generating push disturbance reminding information according to the acquired user account; sending the push disturbance reminding information to a terminal logged in by a task manager account; receiving a forced push instruction returned by a terminal logged in by a task manager account according to the push disturbance reminding information; and executing the application pushing task by taking the obtained user account as a target user account according to the forced pushing instruction.
In an embodiment, according to the forced push instruction, after the application push task is executed with the acquired user account as the target user account, the processor further executes the following steps: extracting a user account corresponding to the executed application pushing task; judging whether the extracted user account is a push limitation account; if not, extracting the push information type in the executed application push task; and updating the extracted historical push records corresponding to the user accounts according to the extracted push information types.
In one embodiment, the processor further performs the steps of: receiving a push limit list configuration instruction sent by a terminal logged in by a task manager account; extracting a user account in a push restriction list configuration instruction; and creating a pushing user restricted list according to the extracted user account.
In this embodiment, the push information type and the user account in the application push task are extracted, a history push record corresponding to the extracted push information type and the extracted user account is queried, push times corresponding to the user accounts are counted according to the history record, the user accounts with the push times smaller than a preset push time are screened and counted from the extracted user accounts, and the application push task is executed according to the screened user accounts. The user accounts are screened according to the pushing times, the screened users corresponding to the user accounts can be guaranteed to be users who receive the pushing information of the extracted pushing information type less than the preset pushing times, the screened users corresponding to the user accounts can be guaranteed not to frequently receive the pushing information of the same pushing information type, and therefore the situation that the number of the users of the application is reduced due to the fact that the screened user accounts frequently receive the pushing information of the same pushing information type and the application is unloaded is avoided.
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 a computer program, which can be stored in a computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the computer program is executed. The storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a Random Access Memory (RAM).
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within 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 invention, 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 inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (8)
1. An application information pushing method, the method comprising:
acquiring an application pushing task;
extracting a push information type and a user account in the application push task;
inquiring historical push records according to the extracted push information types and the user accounts;
counting the pushed times corresponding to each user account according to the inquired historical pushing records;
screening and counting user accounts with the pushed times smaller than the preset pushed times from the extracted user accounts;
executing the application pushing task according to the screened user account;
obtaining the remaining screened user accounts from the extracted user accounts;
extracting the pushed times corresponding to the acquired user account, and generating pushing disturbance reminding information according to the acquired user account and the pushed times corresponding to the acquired user account;
sending the push disturbance reminding information to a terminal logged in by a task manager account;
receiving a forced push instruction returned by the terminal logged in by the task manager account according to the push disturbance reminding information;
according to the forced pushing instruction, the obtained user account is used as a target user account to execute the application pushing task; the method comprises the following steps: extracting each user account in the obtained user accounts, and respectively taking each extracted user account as a target user account to create an application pushing subtask;
and extracting the read push information and the user account in the application push subtask, inquiring the terminal logged with the extracted user account, and sending the extracted push information to the inquired terminal.
2. The method according to claim 1, wherein after extracting the push information type and the user account in the application push task, the method further comprises:
acquiring a push type restriction list;
inquiring the extracted push information type in the push type limit list;
if the application pushing task is not inquired, judging that the application pushing task is not limited by pushing, and executing the application pushing task according to the extracted user account;
if the query is received, judging that the application pushing task is the application pushing task limited by pushing, and executing the step of querying the historical pushing record according to the extracted pushing information type and the user account.
3. The method according to claim 1, wherein after the executing the application push task with the obtained user account as a target user account according to the forced push instruction, the method further includes:
extracting a user account corresponding to the executed application pushing task;
judging whether the extracted user account is a push limitation account;
if yes, extracting the push information type in the executed application push task;
and updating the historical push records corresponding to the extracted user accounts according to the types of the extracted push information.
4. The method of claim 3, further comprising:
receiving a push limit list configuration instruction sent by a terminal logged in by a task manager account;
extracting a user account in the push restriction list configuration instruction;
creating a pushing user restricted list according to the extracted user account;
the judging whether the extracted user account is a push limitation account includes:
acquiring a push user restriction list;
and judging whether the extracted user account is a push limited account or not according to the push user limited list.
5. An application information pushing apparatus, the apparatus comprising:
the push task acquisition module is used for acquiring an application push task;
the push task analysis module is used for extracting a push information type and a user account in the application push task;
the pushing record query module is used for querying a historical pushing record according to the extracted pushing information type and the user account;
the pushing times counting module is used for counting the pushing times corresponding to the user accounts according to the inquired historical pushing records;
the pushing times comparing module is used for screening and counting the user accounts with the pushing times smaller than the preset pushing times from the extracted user accounts;
the pushing task execution module is used for executing the application pushing task according to the screened user account;
the user account acquisition module is used for acquiring the remaining screened user accounts from the extracted user accounts;
the reminding information generating module is used for extracting the pushed times corresponding to the acquired user account, and generating pushing disturbing reminding information according to the acquired user account and the pushed times corresponding to the acquired user account;
the reminding information sending module is used for sending the push disturbing reminding information to a terminal logged in by a task manager account;
the pushing instruction pushing module is used for receiving a forced pushing instruction returned by the terminal logged in by the task manager account according to the pushing disturbance reminding information;
the push task execution module is further used for executing the application push task by taking the obtained user account as a target user account according to the forced push instruction; the method comprises the following steps: extracting each user account in the obtained user accounts, and respectively taking each extracted user account as a target user account to create an application pushing subtask;
and extracting the read push information and the user account in the application push subtask, inquiring the terminal logged with the extracted user account, and sending the extracted push information to the inquired terminal.
6. The apparatus of claim 5, further comprising:
the restriction list acquisition module is used for acquiring a push type restriction list;
the information type query module is used for querying the extracted push information type in the push type limit list;
the push task execution module is further used for judging that the application push task is an application push task which is not limited by push if the extracted push information type is not inquired in the push type limit list, and executing the application push task according to the extracted user account;
the push record query module is further configured to determine that the application push task is an application push task limited by pushing if the extracted push information type is queried in the push type limitation list, and query a historical push record according to the extracted push information type and the user account.
7. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
acquiring an application pushing task;
extracting a push information type and a user account in the application push task;
inquiring historical push records according to the extracted push information types and the user accounts;
counting the pushed times corresponding to each user account according to the inquired historical pushing records;
screening and counting user accounts with the pushed times smaller than the preset pushed times from the extracted user accounts;
executing the application pushing task according to the screened user account;
obtaining the remaining screened user accounts from the extracted user accounts;
extracting the pushed times corresponding to the acquired user account, and generating pushing disturbance reminding information according to the acquired user account and the pushed times corresponding to the acquired user account;
sending the push disturbance reminding information to a terminal logged in by a task manager account;
receiving a forced push instruction returned by the terminal logged in by the task manager account according to the push disturbance reminding information;
according to the forced pushing instruction, the obtained user account is used as a target user account to execute the application pushing task; the method comprises the following steps: extracting each user account in the obtained user accounts, and respectively taking each extracted user account as a target user account to create an application pushing subtask;
and extracting the read push information and the user account in the application push subtask, inquiring the terminal logged with the extracted user account, and sending the extracted push information to the inquired terminal.
8. One or more storage media storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of:
acquiring an application pushing task;
extracting a push information type and a user account in the application push task;
inquiring historical push records according to the extracted push information types and the user accounts;
counting the pushed times corresponding to each user account according to the inquired historical pushing records;
screening and counting user accounts with the pushed times smaller than the preset pushed times from the extracted user accounts;
executing the application pushing task according to the screened user account;
obtaining the remaining screened user accounts from the extracted user accounts;
extracting the pushed times corresponding to the acquired user account, and generating pushing disturbance reminding information according to the acquired user account and the pushed times corresponding to the acquired user account;
sending the push disturbance reminding information to a terminal logged in by a task manager account;
receiving a forced push instruction returned by the terminal logged in by the task manager account according to the push disturbance reminding information;
according to the forced pushing instruction, the obtained user account is used as a target user account to execute the application pushing task; the method comprises the following steps: extracting each user account in the obtained user accounts, and respectively taking each extracted user account as a target user account to create an application pushing subtask;
and extracting the read push information and the user account in the application push subtask, inquiring the terminal logged with the extracted user account, and sending the extracted push information to the inquired terminal.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710608519.1A CN107733968B (en) | 2017-07-24 | 2017-07-24 | Application information pushing method and device, computer equipment and storage medium |
| PCT/CN2018/078312 WO2019019642A1 (en) | 2017-07-24 | 2018-03-07 | Application information pushing method and apparatus, and computer device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710608519.1A CN107733968B (en) | 2017-07-24 | 2017-07-24 | Application information pushing method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107733968A CN107733968A (en) | 2018-02-23 |
| CN107733968B true CN107733968B (en) | 2020-05-29 |
Family
ID=61201296
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710608519.1A Active CN107733968B (en) | 2017-07-24 | 2017-07-24 | Application information pushing method and device, computer equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107733968B (en) |
| WO (1) | WO2019019642A1 (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107733968B (en) * | 2017-07-24 | 2020-05-29 | 深圳壹账通智能科技有限公司 | Application information pushing method and device, computer equipment and storage medium |
| CN110619534A (en) * | 2018-06-19 | 2019-12-27 | 华为技术有限公司 | Marketing information pushing method and device and readable storage medium |
| CN109636475A (en) * | 2018-12-14 | 2019-04-16 | 平安城市建设科技(深圳)有限公司 | Source of houses method for refreshing, device, equipment and storage medium |
| CN110060099B (en) * | 2019-04-04 | 2021-07-20 | 北京字节跳动网络技术有限公司 | Information pushing method and device based on historical records and electronic equipment |
| CN110490651B (en) * | 2019-08-14 | 2023-11-14 | 平安科技（深圳）有限公司 | Information pushing method, device, equipment and computer readable storage medium |
| CN110751168A (en) * | 2019-09-03 | 2020-02-04 | 深圳壹账通智能科技有限公司 | Information pushing method and device, computer equipment and storage medium |
| CN110708360A (en) * | 2019-09-17 | 2020-01-17 | Oppo广东移动通信有限公司 | Information processing method and system and electronic equipment |
| CN113362095A (en) * | 2020-03-05 | 2021-09-07 | 北京沃东天骏信息技术有限公司 | Information delivery method and device |
| CN112380266A (en) * | 2020-10-16 | 2021-02-19 | 广州市百果园网络科技有限公司 | Message data processing method, device, equipment and storage medium |
| CN112804134B (en) * | 2020-12-31 | 2022-10-04 | 深圳市镜玩科技有限公司 | Task initiating method based on instant messaging, related device, equipment and medium |
| CN114115654A (en) * | 2021-10-29 | 2022-03-01 | 北京蓝莓时节科技有限公司 | Method, device, system and storage medium for improving content creation rate of user |
| CN114363408A (en) * | 2021-12-31 | 2022-04-15 | 北京金堤科技有限公司 | Information pushing method and device, computer readable medium and computer equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014194700A1 (en) * | 2013-06-05 | 2014-12-11 | Tencent Technology (Shenzhen) Company Limited | Prompt method for adding quick link in browser, device and system thereof |
| CN104717616A (en) * | 2013-12-13 | 2015-06-17 | 腾讯科技（深圳）有限公司 | Push message management method and device |
| CN104735150A (en) * | 2015-03-27 | 2015-06-24 | 努比亚技术有限公司 | Message pushing method and device |
| CN105589877A (en) * | 2014-10-23 | 2016-05-18 | 腾讯科技（深圳）有限公司 | Information push method and application platform |
| CN105847447A (en) * | 2016-06-01 | 2016-08-10 | 腾讯科技（深圳）有限公司 | Message push method and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9479387B2 (en) * | 2012-06-22 | 2016-10-25 | Salesforce.Com, Inc. | Methods and systems for priority-based notifications for mobile devices |
| CN103327110B (en) * | 2013-06-28 | 2016-05-25 | 腾讯科技（深圳）有限公司 | A kind of information-pushing method and system |
| CN104980327B (en) * | 2014-04-03 | 2019-05-03 | 腾讯科技（深圳）有限公司 | A kind of information push method and device |
| CN105511876B (en) * | 2015-12-04 | 2019-05-03 | Oppo广东移动通信有限公司 | A kind of processing method and processing device of pushed information |
| CN107733968B (en) * | 2017-07-24 | 2020-05-29 | 深圳壹账通智能科技有限公司 | Application information pushing method and device, computer equipment and storage medium |
-
2017
- 2017-07-24 CN CN201710608519.1A patent/CN107733968B/en active Active
-
2018
- 2018-03-07 WO PCT/CN2018/078312 patent/WO2019019642A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014194700A1 (en) * | 2013-06-05 | 2014-12-11 | Tencent Technology (Shenzhen) Company Limited | Prompt method for adding quick link in browser, device and system thereof |
| CN104717616A (en) * | 2013-12-13 | 2015-06-17 | 腾讯科技（深圳）有限公司 | Push message management method and device |
| CN105589877A (en) * | 2014-10-23 | 2016-05-18 | 腾讯科技（深圳）有限公司 | Information push method and application platform |
| CN104735150A (en) * | 2015-03-27 | 2015-06-24 | 努比亚技术有限公司 | Message pushing method and device |
| CN105847447A (en) * | 2016-06-01 | 2016-08-10 | 腾讯科技（深圳）有限公司 | Message push method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2019019642A1 (en) | 2019-01-31 |
| CN107733968A (en) | 2018-02-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107733968B (en) | Application information pushing method and device, computer equipment and storage medium | |
| USRE48194E1 (en) | Systems and methods for monitoring and applying data related to shareable links associated with content items stored in an online content management service | |
| AU2017202007B2 (en) | Notification feed across multiple client devices | |
| US9690910B2 (en) | Systems and methods for monitoring and applying statistical data related to shareable links associated with content items stored in an online content management service | |
| US9246935B2 (en) | Method and system for dynamic and comprehensive vulnerability management | |
| CN110688598B (en) | Service parameter acquisition method and device, computer equipment and storage medium | |
| CN107679819B (en) | Financial data processing method and device, computer equipment and storage medium | |
| US9514291B2 (en) | Information processing system, information processing device, and authentication information management method | |
| WO2023024835A1 (en) | Context-based consolidation of communications across different communication platforms | |
| US20120221444A1 (en) | Message queue based product asset management auditing system | |
| JP5102650B2 (en) | Information search system, information search method, information search program, and recording medium | |
| US10666834B2 (en) | Information processing system, information processing apparatus, and information processing method | |
| CN109657164B (en) | Method, device and storage medium for publishing message | |
| CN109391537B (en) | Information processing method and device and computer storage medium | |
| JP2020009114A (en) | Image evaluation device, system, and control method and program for image evaluation device | |
| CN114239510A (en) | Service information processing method and device, storage medium and electronic equipment | |
| CN115001967A (en) | Data acquisition method and device, electronic equipment and storage medium | |
| CN110533469B (en) | Advertisement operation method and device, server, intelligent terminal and storage medium | |
| CN111143526B (en) | Method and device for generating and controlling configuration information of counsel service control | |
| CN114036491A (en) | Software management method, system and storage medium | |
| US10922349B1 (en) | Filtering remote access monitoring data | |
| CN111966506A (en) | Content sharing method based on different application programs and computer equipment | |
| CN112860770A (en) | Report generation method and device, electronic equipment and storage medium | |
| CN112417259A (en) | Media resource processing method, device, equipment and storage medium | |
| US11983450B2 (en) | Generating user interface for onboarding |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20180524 Address after: 518000 Room 201, building A, No. 1, Qian Wan Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (Shenzhen Qianhai business secretary Co., Ltd.) Applicant after: Shenzhen one ledger Intelligent Technology Co., Ltd. Address before: 200000 Xuhui District, Shanghai Kai Bin Road 166, 9, 10 level. Applicant before: Shanghai Financial Technologies Ltd |
|
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 518000 Room 201, building A, 1 front Bay Road, Shenzhen Qianhai cooperation zone, Shenzhen, Guangdong Applicant after: Shenzhen one ledger Intelligent Technology Co., Ltd. Address before: 518000 Room 201, building A, No. 1, Qian Wan Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (Shenzhen Qianhai business secretary Co., Ltd.) Applicant before: Shenzhen one ledger Intelligent Technology Co., Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |