WO2019019642A1 - 应用信息推送方法、装置、计算机设备和存储介质 - Google Patents

应用信息推送方法、装置、计算机设备和存储介质 Download PDF

Info

Publication number
WO2019019642A1
WO2019019642A1 PCT/CN2018/078312 CN2018078312W WO2019019642A1 WO 2019019642 A1 WO2019019642 A1 WO 2019019642A1 CN 2018078312 W CN2018078312 W CN 2018078312W WO 2019019642 A1 WO2019019642 A1 WO 2019019642A1
Authority
WO
WIPO (PCT)
Prior art keywords
push
user account
task
application
extracted
Prior art date
Application number
PCT/CN2018/078312
Other languages
English (en)
French (fr)
Inventor
刘浩
Original Assignee
深圳壹账通智能科技有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 深圳壹账通智能科技有限公司 filed Critical 深圳壹账通智能科技有限公司
Publication of WO2019019642A1 publication Critical patent/WO2019019642A1/zh

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
    • 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

Definitions

  • the present application relates to the field of information processing technologies, and in particular, to an application information pushing method, apparatus, computer device, and storage medium.
  • An application information pushing method comprising: acquiring an application push task; extracting a push information type and a user account in the application push task; querying a history push record according to the extracted push information type and the user account; The history push record counts the number of times that each user account corresponds to the number of pushes; the user account whose filter count is less than the preset push times is filtered from the extracted user account; and the application push task is executed according to the selected user account.
  • An application information pushing device comprising: a push task obtaining module, configured to acquire an application push task; a push task parsing module, configured to extract a push information type and a user account in the application push task; and a push record query module
  • the method is used for querying the historical push record according to the extracted push information type and the user account;
  • the push count statistics module is configured to count the number of pushed times corresponding to each user account according to the historical push record that is queried;
  • the push count comparison module is used for The user account that is filtered from the extracted user account is less than the preset number of pushes;
  • the push task execution module is configured to execute the application push task according to the filtered user account.
  • a computer device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor executing the computer program to implement the following steps: acquiring an application Pushing the task; extracting the push information type and the user account in the application push task; querying the historical push record according to the extracted push information type and the user account; and counting the number of push times corresponding to each user account according to the queried historical push record The user account whose filtering count is less than the preset number of push times is filtered from the extracted user account; and the application push task is executed according to the filtered user account.
  • One or more storage media storing computer-executable instructions, when executed by one or more processors, causing the one or more processors to perform the steps of: acquiring an application push task; extracting The push information type and the user account in the application push task are described; the history push record is queried according to the extracted push information type and the user account; and the pushed times corresponding to each user account are counted according to the queried historical push record; The user account in the user account is filtered according to the preset number of push times; the application push task is executed according to the selected user account.
  • the application information pushing method, device, computer device and storage medium can ensure that the user corresponding to the selected user account is the user who receives the push information of the extracted push information type less than the preset push times, and ensures the screening.
  • the user corresponding to the user account does not frequently receive the push message of the same push information type, thereby avoiding that the filtered user account uninstalls the application because the push message of the same push information type is frequently received.
  • FIG. 1 is an application environment diagram of an application information pushing method in an embodiment
  • FIG. 2 is a structural block diagram of a server in an application information push system in an embodiment
  • FIG. 3 is a schematic flowchart of an application information pushing method in an embodiment
  • FIG. 4 is a flow chart showing the steps of detecting the type of push information in an embodiment
  • FIG. 5 is a schematic flowchart of a step of generating push disturbing reminder information in an embodiment
  • FIG. 6 is a flow chart showing the steps of updating a history push record in an embodiment
  • FIG. 7 is a structural block diagram of an application information pushing apparatus in an embodiment
  • FIG. 8 is a structural block diagram of an application information pushing apparatus in another embodiment
  • Figure 9 is a block diagram showing the structure of an application information pushing apparatus in still another embodiment.
  • FIG. 1 is an application environment diagram of an application information pushing method in an embodiment.
  • the application information pushing method is applied to an application information pushing system.
  • the application information push system includes a terminal 110 and a server 120, wherein the terminal 110 is connected to the server 120 through a network.
  • the terminal 110 may be a fixed terminal or a mobile terminal, and the fixed terminal may specifically be at least one of a printer, a scanner, and a monitor, and the mobile terminal may specifically be at least one of a tablet computer, a smart phone, a personal data assistant, and a digital camera. .
  • FIG. 2 is a schematic diagram showing the internal structure of the server 120 in the application information pushing system of FIG. 1 in an embodiment.
  • the server 120 includes a processor, a non-volatile storage medium, an internal memory, and a network interface connected by a system bus.
  • the processor of 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.
  • the network interface is used for network communication with terminal 110.
  • At least one computer executable instruction is stored in the memory, and the computer executable instruction can be executed by the processor to implement the application information pushing method applicable to the server 120 provided in the embodiment of the present application.
  • 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).
  • the memory includes a non-volatile storage medium and an internal memory; the non-volatile storage medium stores an operating system, a database, and computer-executable instructions, and the database stores historical push records corresponding to each user account.
  • the computer executable instructions are executable by a processor to implement the application information push method described above; the internal memory provides a cached operating environment for operating systems and computer executable instructions in a non-volatile storage medium.
  • an application information pushing method is provided.
  • This embodiment is exemplified by the method applied to the server 120 in FIG. 1, and the method specifically includes the following content:
  • the terminal 110 acquires the task administrator account input by the task administrator, generates a push task page request according to the obtained task administrator account, and sends a push task page request to the server 120.
  • the server 120 receives the push task page request sent by the terminal 110, parses the push task page request, and parses the task administrator account in the push task page request to verify whether the extracted task administrator account has access to the push task page. .
  • the server 120 After verifying that the extracted task administrator account has the right to access the push task page, the server 120 obtains the push task page data, and returns the obtained push task page data to the terminal 110 corresponding to the push task page request.
  • 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 the task manager on the push task page.
  • the terminal 110 acquires the push information and the user account input by the task administrator in the push task page according to the push task creation instruction, generates an application push task according to the obtained 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 sent by the terminal 110.
  • the server 120 extracts the type of push information and the user account in the application push task by parsing.
  • the push information type is the type of push information in the application push task.
  • the user account is the target user account in the application task.
  • the database of the server 120 stores a history push record corresponding to the user account.
  • the server 120 queries the historical push record corresponding to the extracted user account in the historical push record in the database, and then queries and extracts the extracted push information type in the historical push record corresponding to the extracted user account.
  • Historical push record a history push record corresponding to the user account.
  • the server 120 may also query the historical push record corresponding to the extracted push information type in the historical push record of the database, and then in the historical push record corresponding to the extracted push information type, query and The historical push record corresponding to the extracted historical push record.
  • the server 120 extracts historical push records corresponding to each user account in the historical push record that is queried, and counts the number of pushed times corresponding to each user account according to the historical push record corresponding to each user account.
  • the user account whose number of pushed statistics is less than the preset number of push times is filtered from the extracted user accounts.
  • the server 120 compares the number of pushed times corresponding to each user account in each extracted user account with the preset number of pushes, and compares and determines the user account whose number of push times is less than the preset push times, and extracts the user account from the extracted user account. The determined user account is selected.
  • S312 Perform an application push task according to the filtered user account.
  • 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 user account in the filtered user account.
  • the created application push subtask corresponds to each user account in the filtered user account.
  • the server 120 extracts the push information in the application push task, creates an application push subtask according to each user account in the filtered user account and extracts the push information, and adds the created application push subtask to the task. In the queue.
  • the server 120 reads the application push subtask from the task queue and executes the read application push subtask.
  • the application information pushing method specifically includes the following content: acquiring a current time point; comparing the current time point with a preset time point; if the current time point is the same as the preset time point, deleting each user account corresponding to Historical push record.
  • the preset time point is set to 0 o'clock every day, and when the server 120 detects that the current time is 0 o'clock, the historical push record corresponding to each user account in the database is deleted.
  • the server 120 can be guaranteed to filter the user account according to the historical push record in one day, and improve the accuracy of screening the user account.
  • the push information type and the user account in the application push task are extracted, and the extracted push information type and the historical push record corresponding to the user account are queried, and the number of push times corresponding to each user account is counted according to the historical record, and the extracted number is extracted.
  • the user account in the user account is counted and the number of pushes is less than the preset number of pushes, and the application push task is executed according to the selected user account. Filtering the user account according to the number of pushes can ensure that the user corresponding to the filtered user account is the user who receives the push information of the extracted push information type less than the preset push times, and ensures the user corresponding to the filtered user account.
  • the push message of the same push information type is not frequently received, so that the filtered user account is prevented from being uninstalled because the push message of the same push information type is frequently received, thereby avoiding the decrease of the number of users of the application.
  • the method further includes the step of detecting a type of push information, where the step specifically includes the following:
  • a push type restriction list is stored in the database of the server 120.
  • the push type restriction list is used to identify whether the push information in the application push task is subject to certain push restrictions.
  • the push type restriction list includes the push information type, and the push type in the push type restriction list is the push information type of the pushed push information.
  • the server 120 obtains a push type restriction list from the database.
  • the server 120 queries the type of the push information in the push type restriction list, and if the query is found, determines that the application push task is an application push task that is not restricted by the push; if not, the query is not performed. Upon that, it is determined that the application push task is an application push task that is restricted by push.
  • the server 120 determines that the application push task is an application push task that is not restricted by the push.
  • the server 120 parses the application push task, extracts the push information in the application push task by parsing, and creates an application push subtask according to each user account and the extracted push information in the extracted user account respectively, and the created application pusher is created. Tasks are added to the task queue.
  • the server 120 reads the application push subtask from the task queue and executes the read application push subtask.
  • the server 120 determines that the application push task is a push-restricted application push task, and needs to limit the application push task according to the historical push record.
  • the server 120 queries the historical push record according to the extracted push information type and the user account, and counts the number of pushes corresponding to each user account according to the queried historical push record, and the number of pushed statistics of the filtered user account is less than the pre-push.
  • the user account with the number of push times is executed, and the application push task is executed according to the selected user account.
  • the application push task corresponding to the type of the pushed push information is restricted.
  • the application push task to be controlled is set by pushing the information type list to improve the control efficiency of the application push task.
  • the number of pushes of the application push task corresponding to the push information type in the push type restriction list to the same user account is controlled, and the user account is prevented from receiving the push information corresponding to the same push information type multiple times.
  • the method further includes the step of generating push interruption reminding information, where the step specifically includes the following:
  • the server 120 selects the user account that has been pushed less than the preset number of pushes from the extracted user account, and obtains the remaining user accounts in the extracted user account.
  • the server 120 filters out the user accounts whose number of pushes is greater than or equal to the preset number of pushes from the extracted user accounts.
  • the server 120 extracts the number of pushed times corresponding to the obtained user account, and generates push reminding reminding information according to the obtained user account and the number of pushed times corresponding to the obtained user account.
  • the push disturbing reminder message is "N has been pushed to the user account A; the user account B has been pushed M times.”
  • the server 120 queries the terminal 120 that is logged in with the task administrator account, and sends the push disturbing reminder information to the queried terminal 110.
  • the terminal 110 displays the push disturbing reminder information on the push task page.
  • the terminal 110 displays a push button on the push task page that pushes the reminder reminder information. After the push administrator determines to push the push reminder information, the push button is clicked through the input device of the terminal 110 when the push is forced to be pushed. When the terminal 110 detects that the forced push button is clicked, the terminal 110 triggers a forced push command. The terminal 110 transmits a forced push command to the server 120.
  • the push task page of the terminal displaying the push disturb reminder information is provided with a give back push button.
  • the push administrator decides to abandon the user account corresponding to the push disturbing reminder information, and then clicks the abandon push button through the input device of the terminal 110.
  • the terminal 110 detects that the abandonment push button is clicked, it triggers the abandonment push command, and the terminal 110 sends the triggered abandonment push command to the server 120.
  • the server 120 discards the information push of the acquired user account according to the abandonment push command.
  • the server 120 uses the obtained user account as the target user account of the application push task to perform application push.
  • the server 120 extracts each user account in the acquired user account, creates an application push subtask with each extracted user account as the target user account, and adds the created application push subtask to the task. In the queue.
  • the server 120 can read the application push subtask from the task queue according to the preset read data, and execute the read application push subtask in parallel.
  • the server 120 extracts the pushed information and the user account in the read application subtask, queries the terminal that has the extracted user account, and sends the extracted push information to the queried terminal.
  • the push disturbing reminder information is generated according to the obtained user account, and the push disturbing reminding information is sent to the terminal that is logged in by the task administrator account, so as to ensure that the task administrator can determine whether the obtained information is obtained according to the disturbing reminding information.
  • User account for information push is generated according to the obtained user account, and the push disturbing reminding information is sent to the terminal that is logged in by the task administrator account, so as to ensure that the task administrator can determine whether the obtained information is obtained according to the disturbing reminding information.
  • the method further includes the step of updating the historical push record, and the step specifically includes the following:
  • the server 120 marks the application push task as executed.
  • the server 120 parses the executed application push task, and extracts the user account in the executed application push task by parsing.
  • the push restriction account is stored in the database of the server 120.
  • the server 120 queries the extracted user account in the stored push restriction account. If the extracted user account is queried in the push restriction account, it is determined that the extracted user account is a push restriction account.
  • the server 120 parses the executed application push task, and extracts the type of push information in the executed application push task by parsing.
  • the server 120 queries the extracted user account and the push information type corresponding historical push record, and updates the pushed times in the queried historical push record.
  • the server 120 acquires the push time of the pushed application push task, and stores the corresponding push time, the user account extracted from the pushed application push task, and the push information type as the historical push record. .
  • the application pushing method further includes: receiving a push restriction list configuration instruction sent by the terminal logged in by the task administrator account; extracting a user account in the push restriction list configuration instruction; and creating a push user according to the extracted user account. Limit list.
  • S604 specifically includes: obtaining a push user restriction list; determining, according to the push user restriction list, whether the extracted user account is a push restriction account.
  • the terminal 110 that is logged in with the task administrator account obtains the user account that is to be configured as the push restriction account, and generates a push restriction list configuration command according to the obtained account, and sends the push restriction list configuration command to the server 120.
  • the server 120 parses the push restriction list configuration command, parses and extracts the user account in the push restriction list configuration command, and creates a push user restriction list according to the extracted user account.
  • the server 120 obtains a push user restriction list, and determines whether the user account is a push restriction account according to the push user restriction list.
  • the user account in the executed application push task is determined to be a push restriction account, and the historical push record corresponding to the user account is updated according to the push information type in the executed application push task to ensure the accuracy of the history push record. Improves the accuracy of screening user accounts based on historical push records.
  • an application information pushing apparatus 700 is provided.
  • the apparatus specifically includes the following contents: a push task obtaining module 702, a push task parsing module 704, a push record query module 706, and a push count counting module. 708.
  • the push task obtaining module 702 is configured to acquire an application push task.
  • the push task parsing module 704 is configured to extract the push information type and the user account in the application push task.
  • the push record query module 706 is configured to query the historical push record according to the extracted push information type and the user account.
  • the push count statistics module 708 is configured to count the number of pushed times corresponding to each user account according to the queried historical push record.
  • the push times comparison module 710 is configured to filter the counted user accounts whose number of pushed times is less than the preset push times from the extracted user accounts.
  • the push task execution module 712 is configured to execute an application push task according to the filtered user account.
  • the push information type and the user account in the application push task are extracted, and the extracted push information type and the historical push record corresponding to the user account are queried, and the number of push times corresponding to each user account is counted according to the historical record, and the extracted number is extracted.
  • the user account in the user account is counted and the number of pushes is less than the preset number of pushes, and the application push task is executed according to the selected user account. Filtering the user account according to the number of pushes can ensure that the user corresponding to the filtered user account is the user who receives the push information of the extracted push information type less than the preset push times, and ensures the user corresponding to the filtered user account.
  • the push message of the same push information type is not frequently received, thereby avoiding that the filtered user account uninstalls the application because the push message of the same push information type is frequently received, resulting in a situation in which the number of users of the application is reduced.
  • the application information pushing apparatus 700 specifically includes the following content: a restriction list obtaining module 714 and an information type query module 716.
  • the restriction list obtaining module 714 is configured to obtain a push type restriction list.
  • the information type query module 716 is configured to query the extracted push information type in the push type restriction list.
  • the push task execution module 712 is further configured to: if the extracted push information type is not queried in the push type restriction list, determine that the application push task is an application push task that is not restricted by push, and execute an 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 restriction list, determine that the application push task is a push-restricted application push task, and according to the extracted push information type and the user account query history push recording.
  • the application push task corresponding to the type of the pushed push information is restricted.
  • the application push task to be controlled is set by pushing the information type list to improve the control efficiency of the application push task. Controls the number of pushes of the application push task corresponding to the push information type in the push type restriction list to the same user account, and prevents the user account from receiving the push information corresponding to the same push information type multiple times.
  • the application information pushing apparatus 700 further includes the following contents: a user account obtaining module 718 , a reminding information generating module 720 , a reminding information sending module 722 , and a push instruction pushing module 724 .
  • the user account obtaining module 718 is configured to obtain the user account remaining after the screening from the extracted user accounts.
  • the reminder information generating module 720 is configured to generate push disturbing reminder information according to the obtained user account.
  • the reminder information sending module 722 is configured to send the push disturbing reminder information to the terminal that is logged in with the task administrator account.
  • the push command pushing module 724 is configured to receive a forced push command returned by the terminal logged in by the task administrator account according to the push disturbing reminder information.
  • the push task execution module 712 is further configured to perform an application push task by using the obtained user account as the target user account according to the forced push instruction.
  • the push disturbing reminder information is generated according to the obtained user account, and the push disturbing reminder information is sent to the terminal registered by the task administrator account. Therefore, the task administrator may be prompted to push and disturb the user account, so as to ensure that the task administrator can decide whether to push the information of the obtained user account according to the disturbing reminder information.
  • the push record query module 706 is further configured to: extract a user account corresponding to the executed application push task; determine whether the extracted user account is a push limit account; and if it is determined that the extracted user account is a push limit account, Extracting the type of push information in the executed application push task; updating the historical push record corresponding to the extracted user account according to the extracted push information type.
  • the method for determining whether the extracted user account is a push restriction account includes: obtaining a push user restriction list; and determining, according to the push user restriction list, whether the extracted user account is a push restriction account.
  • the application information pushing apparatus 700 specifically includes a restriction list creation module.
  • the restriction list creation module is configured to receive a push restriction list configuration instruction sent by the terminal logged in by the task administrator account; extract the user account in the push restriction list configuration instruction; and create a push user restriction list according to the extracted user account.
  • the user account in the executed application push task is determined to be a push restriction account, and the historical push record corresponding to the user account is updated according to the push information type in the executed application push task to ensure the accuracy of the history push record. Improves the accuracy of screening user accounts based on historical push records.
  • a computer device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor executing the computer program to: obtain an application push task; and extract the push in the application push task Information type and user account; query historical push record according to the type of push information extracted and user account; count the number of pushes corresponding to each user account according to the historical push record of the query; filter the statistics from the extracted user account The user account whose number of pushes is less than the preset number of pushes; the application push task is executed according to the selected user account.
  • the processor after extracting the type of push information and the user account in the application push task, the processor further implements the following steps: obtaining a push type restriction list; and querying the extracted push information type in the push type restriction list. If not found, the application push task is determined to be an application push task that is not restricted by the push, and the application push task is executed according to the extracted user account; if the query is found, the application push task is determined to be a push-restricted application push task. The step of querying the historical push record according to the extracted push information type and the user account is performed.
  • the processor after executing the application push task according to the filtered user account, the processor further implements the following steps: obtaining the user account remaining after the filtering from the extracted user account; and obtaining the user account according to the obtained user account Generating the push disturbing reminder information; sending the push disturbing reminder information to the terminal registered with the task administrator account; receiving the forced push instruction returned by the terminal registered by the task administrator account according to the push disturbing reminding information; according to the forced pushing instruction, obtaining The user account performs the application push task as the target user account.
  • the processor further executes the following steps: extracting the user account corresponding to the executed application push task; Determining whether the extracted user account is a push restriction account; if not, extracting the type of push information in the executed application push task; and updating the historical push record corresponding to the extracted user account according to the extracted push information type.
  • the processor executes the computer program, the following steps are further performed: receiving a push restriction list configuration instruction sent by the terminal logged in by the task administrator account; extracting a user account in the push restriction list configuration instruction; according to the extracted user The account creates a list of push user restrictions.
  • the method for determining whether the extracted user account is a push restriction account includes: obtaining a push user restriction list; and determining, according to the push user restriction list, whether the extracted user account is a push restriction account.
  • the push information type and the user account in the application push task are extracted, and the extracted push information type and the historical push record corresponding to the user account are queried, and the number of push times corresponding to each user account is counted according to the historical record, and the extracted number is extracted.
  • the user account in the user account is counted and the number of pushes is less than the preset number of pushes, and the application push task is executed according to the selected user account. Filtering the user account according to the number of pushes can ensure that the user corresponding to the filtered user account is the user who receives the push information of the extracted push information type less than the preset push times, and ensures the user corresponding to the filtered user account.
  • the push message of the same push information type is not frequently received, thereby avoiding that the filtered user account uninstalls the application because the push message of the same push information type is frequently received, resulting in a situation in which the number of users of the application is reduced.
  • One or more storage media storing computer executable instructions that, when executed by one or more processors, cause one or more processors to perform the steps of: obtaining an application push task; extracting an application push task Pushing the information type and the user account; querying the historical push record according to the extracted push information type and the user account; counting the pushed times corresponding to each user account according to the historical push record obtained by the query; and filtering the statistics from the extracted user accounts The user account that has been pushed less than the preset number of pushes; performs the application push task according to the selected user account
  • the processor after extracting the type of push information and the user account in the application push task, the processor further implements the following steps: obtaining a push type restriction list; and querying the extracted push information type in the push type restriction list. If not found, the application push task is determined to be an application push task that is not restricted by the push, and the application push task is executed according to the extracted user account; if the query is found, the application push task is determined to be a push-restricted application push task. The step of querying the historical push record according to the extracted push information type and the user account is performed.
  • the processor after performing the application push task according to the selected user account, the processor further performs the following steps: obtaining the user account remaining after the screening from the extracted user account; and generating a push interruption reminder according to the obtained user account.
  • the information is sent to the terminal that is logged in as the task administrator account; the terminal that is logged in with the task administrator account receives the forced push instruction returned according to the push disturbing reminder information; according to the forced push command, the obtained user account is used as the information
  • the target user account performs an application push task.
  • the processor after performing the application push task with the obtained user account as the target user account according to the forced push instruction, the processor further performs the following steps: extracting the user account corresponding to the executed application push task; and determining the extracted Whether the user account is a push restriction account; if not, extracting the type of push information in the executed application push task; and updating the historical push record corresponding to the extracted user account according to the extracted push information type.
  • the processor further performs the steps of: receiving a push restriction list configuration instruction sent by the terminal logged in by the task administrator account; extracting a user account in the push restriction list configuration instruction; and creating a push user according to the extracted user account. Limit list.
  • the push information type and the user account in the application push task are extracted, and the extracted push information type and the historical push record corresponding to the user account are queried, and the number of push times corresponding to each user account is counted according to the historical record, and the extracted number is extracted.
  • the user account in the user account is counted and the number of pushes is less than the preset number of pushes, and the application push task is executed according to the selected user account. Filtering the user account according to the number of pushes can ensure that the user corresponding to the filtered user account is the user who receives the push information of the extracted push information type less than the preset push times, and ensures the user corresponding to the filtered user account.
  • the push message of the same push information type is not frequently received, thereby avoiding that the filtered user account uninstalls the application because the push message of the same push information type is frequently received, resulting in a situation in which the number of users of the application is reduced.
  • 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).

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种应用信息推送方法、装置、计算机设备和存储介质，所述方法包括：获取应用推送任务；提取所述应用推送任务中的推送信息类型和用户账号；根据提取到的推送信息类型和用户账号查询历史推送记录；根据查询到的历史推送记录统计各用户账号分别对应的已推送次数；从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号；根据筛选到的用户账号执行所述应用推送任务。所述应用信息推送方法避免了筛选到的用户账号因为频繁接收到同一推送信息类型的推送消息而将应用卸载，避免了应用的用户数量减少的情况。

Description

应用信息推送方法、装置、计算机设备和存储介质
本申请申明享有2017年7月24日递交的申请号为201710608519.1、名称为“应用信息推送方法、装置、计算机设备和存储介质”的中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请涉及信息处理技术领域，特别是涉及一种应用信息推送方法、装置、计算机设备和存储介质。
背景技术
随着互联网技术和计算机技术的迅猛发展，越来越多的应用程序被开发出来，被开发出来的应用程序被安装在终端中。各种应用信息可以通过互联网向安装有应用程序的终端推送，以便用户通过终端可以及时获取到相关的应用信息。随着应用信息推送需求的不断增加，通过互联网进行应用信息推送的任务量也增加，用户收到推送的应用信息也随之增加。应用消息的推送频率太过频繁，会导致用户将推送频率太过频繁的应用卸载，导致应用对应的用户数量减少。
发明内容
基于此，有必要针对应用的用户数量减少的问题，提供一种应用信息推送方法、装置、计算机设备和存储介质。
一种应用信息推送方法，所述方法包括：获取应用推送任务；提取所述应用推送任务中的推送信息类型和用户账号；根据提取到的推送信息类型和用户账号查询历史推送记录；根据查询到的历史推送记录统计各用户账号分别对应的已推送次数；从提取到的用户账号中筛选统计的已推送次数小于预 设推送次数的用户账号；根据筛选到的用户账号执行所述应用推送任务。
一种应用信息推送装置，所述装置包括：推送任务获取模块，用于获取应用推送任务；推送任务解析模块，用于提取所述应用推送任务中的推送信息类型和用户账号；推送记录查询模块，用于根据提取到的推送信息类型和用户账号查询历史推送记录；推送次数统计模块，用于根据查询到的历史推送记录统计各用户账号分别对应的已推送次数；推送次数比较模块，用于从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号；推送任务执行模块，用于根据筛选到的用户账号执行所述应用推送任务。
一种计算机设备，所述计算机设备包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现以下步骤：获取应用推送任务；提取所述应用推送任务中的推送信息类型和用户账号；根据提取到的推送信息类型和用户账号查询历史推送记录；根据查询到的历史推送记录统计各用户账号分别对应的已推送次数；从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号；根据筛选到的用户账号执行所述应用推送任务。
一个或多个存储有计算机可执行指令的存储介质，所述计算机可执行指令被一个或多个处理器执行时，使得所述一个或多个处理器执行以下步骤：获取应用推送任务；提取所述应用推送任务中的推送信息类型和用户账号；根据提取到的推送信息类型和用户账号查询历史推送记录；根据查询到的历史推送记录统计各用户账号分别对应的已推送次数；从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号；根据筛选到的用户账号执行所述应用推送任务。
上述应用信息推送方法、装置、计算机设备和存储介质，可以保证筛选到的用户账号所对应用户为接收到与提取到的推送信息类型的推送信息的次数小于预设推送次数的用户，保证筛选到的用户账号所对应的用户不会频繁接收到同一推送信息类型的推送消息，从而也避免了筛选到的用户账号因 为频繁接收到同一推送信息类型的推送消息而将应用卸载。
附图说明
图1为一个实施例中应用信息推送方法的应用环境图；
图2为一个实施例中应用信息推送系统中的服务器的结构框图；
图3为一个实施例中应用信息推送方法的流程示意图；
图4为一个实施例中检测推送信息类型的步骤的流程示意图；
图5为一个实施例中生成推送打扰提醒信息的步骤的流程示意图；
图6为一个实施例中更新历史推送记录的步骤的流程示意图；
图7为一个实施例中应用信息推送装置的结构框图；
图8为另一个实施例中应用信息推送装置的结构框图；
图9为再一个实施例中应用信息推送装置的结构框图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
图1为一个实施例中应用信息推送方法的应用环境图。参照图1，该应用信息推送方法应用于应用信息推送系统。应用信息推送系统包括终端110和服务器120，其中终端110通过网络与服务器120连接。终端110可以是固定终端或移动终端，固定终端具体可以是打印机、扫描仪和监控器中的至少一种，移动终端具体可以是平板电脑、智能手机、个人数据助理和数码相机中的至少一种。
图2为一个实施例中图1应用信息推送系统中的服务器120的内部结构示意图。如图2所示，该服务器120包括通过系统总线连接的处理器、非易失性存储介质、内存储器和网络接口。服务器120的处理器用于提供计算和 控制能力，支撑整个服务器120的运行，存储器用于存储数据、代码指令等，网络接口用于与终端110进行网络通信。存储器上存储有至少一个计算机可执行指令，该计算机可执行指令可被处理器执行，以实现本申请实施例中提供的适用于服务器120的应用信息推送方法。存储器可包括磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)等非易失性存储介质，或随机存储记忆体(Random Access Memory，RAM)等。例如，在一个实施例中，存储器包括非易失性存储介质及内存储器；非易失性存储介质存储有操作系统、数据库和计算机可执行指令，数据库存储着各用户账号对应的历史推送记录，该计算机可执行指令可被处理器执行以实现上述的应用信息推送方法；内存储器为非易失性存储介质中的操作系统及计算机可执行指令提供高速缓存的运行环境。
如图3所示，在一个实施例中，提供一种应用信息推送方法，本实施例以该方法应用于图1中的服务器120来举例说明，该方法具体包括以下内容：
S302，获取应用推送任务。
具体地，终端110获取任务管理员输入的任务管理员账号，根据获取到的任务管理员账号生成推送任务页面请求，将推送任务页面请求发送至服务器120。服务器120接收终端110发送的推送任务页面请求，对推送任务页面请求进行解析，通过解析提取推送任务页面请求中的任务管理员账号，验证提取到的任务管理员账号是否有访问推送任务页面的权限。服务器120在验证提取到的任务管理员账号有访问推送任务页面的权限后，获取推送任务页面数据，将获取到的推送任务页面数据返回至推送任务页面请求对应的终端110。终端110接收到服务器120返回的推送任务页面数据，根据推送任务页面数据显示推送任务页面。终端110检测到任务管理员在推送任务页面触发的推送任务创建指令。终端110根据推送任务创建指令获取任务管理员在推送任务页面中输入的推送信息和用户账号，根据获取到的推送信息和用户账号生成应用推送任务，将生成的应用推送任务发送至服务器120。服务 器120接收终端110发送的应用推送任务。
S304，提取应用推送任务中的推送信息类型和用户账号。
具体地，服务器120通过解析提取应用推送任务中的推送信息类型和用户账号。推送信息类型为应用推送任务中的推送信息所属类型。用户账号为应用任务中的目标用户账号。
S306，根据提取到的推送信息类型和用户账号查询历史推送记录。
具体地，服务器120的数据库中存储着用户账号对应的历史推送记录。服务器120在数据库中的历史推送记录中，先查询与提取到的用户账号对应的历史推送记录，再在与提取到的用户账号对应的历史推送记录中，查询与提取到的推送信息类型对应的历史推送记录。
在一个实施例中，服务器120还可以在数据库的历史推送记录中，先查询与提取到的推送信息类型对应的历史推送记录，再在于提取到的推送信息类型对应的历史推送记录中，查询与提取到的历史推送记录对应的历史推送记录。
S308，根据查询到的历史推送记录统计各用户账号分别对应的已推送次数。
具体地，服务器120在查询到的历史推送记录中，分别提取各用户账号对应的历史推送记录，根据各用户账号对应的历史推送记录分别统计各用户账号对应的已推送次数。
S310，从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号。
具体地，服务器120将提取到的各用户账号中各用户账号对应的已推送次数与预设推送次数相比较，通过比较确定已推送次数小于预设推送次数的用户账号，从提取到的用户账号中筛选出确定的用户账号。
S312，根据筛选到的用户账号执行应用推送任务。
具体地，服务器120提取应用推送任务中的推送信息，根据提取到的推 送信息和筛选到的用户账号中的每个用户账号创建应用推送子任务。其中，创建的应用推送子任务与筛选到的用户账号中的每个用户账号一一对应。
在一个实施例中，服务器120提取应用推送任务中的推送信息，根据筛选到的用户账号中的每个用户账号和提取到推送信息创建应用推送子任务，将创建的应用推送子任务添加到任务队列中。服务器120从任务队列中读取应用推送子任务，执行读取到的应用推送子任务。
在一个实施例中，应用信息推送方法具体还包括以下内容：获取当前时间点；将当前时间点与预设时间点进行比较；若当前时间点与预设时间点相同，则删除各用户账号对应的历史推送记录。
举例说明，预设时间点设置为每天0点，服务器120检测到当前时间为0点时，删除数据库中各用户账号对应的历史推送记录。可以保证服务器120根据一天内的历史推送记录筛选用户账号，提高筛选用户账号的准确性。
本实施例中，提取应用推送任务中推送信息类型和用户账号，查询与提取到的推送信息类型和用户账号对应的历史推送记录，根据历史记录统计各用户账号对应的推送次数，从提取到的用户账号中筛选统计到的推送次数小于预设推送次数的用户账号，根据筛选到的用户账号执行应用推送任务。根据推送次数筛选用户账号，可以保证筛选到的用户账号所对应用户为接收到与提取到的推送信息类型的推送信息的次数小于预设推送次数的用户，保证筛选到的用户账号所对应的用户不会频繁接收到同一推送信息类型的推送消息，从而也避免了筛选到的用户账号因为频繁接收到同一推送信息类型的推送消息而将应用卸载，避免了应用的用户数量减少的情况。
如图4所示，在一个实施例中，S304之后具体还包括检测推送信息类型的步骤，该步骤具体包括以下内容：
S402，获取推送类型限制列表。
具体地，服务器120的数据库中存储着推送类型限制列表。推送类型限制列表用于识别应用推送任务中推送信息是否受到一定的推送限制。推送类 型限制列表中包括推送信息类型，推送类型限制列表中的推送信息类型为受到限制的推送信息的推送信息类型。服务器120从数据库中获取推送类型限制列表。
S404，在推送类型限制列表中查询提取到的推送信息类型。
具体地，服务器120在获取到推送类型限制列表后，在推送类型限制列表中查询提取到的推送信息类型，若查询到，则判定应用推送任务为不受推送限制的应用推送任务；若未查询到，则判定应用推送任务为受推送限制的应用推送任务。
S406，若在推送类型限制列表中未查询到提取到的推送信息类型，则判定应用推送任务为不受推送限制的应用推送任务，根据提取到的用户账号执行应用推送任务。
具体地，服务器120在推送类型限制列表未查询到提取到的推送信息类型时，判定应用推送任务为不受推送限制的应用推送任务。服务器120对应用推送任务解析，通过解析提取应用推送任务中的推送信息，分别根据提取到的用户账号中的每个用户账号和提取到的推送信息创建应用推送子任务，将创建的应用推送子任务添加到任务队列中。服务器120从任务队列中读取应用推送子任务，执行读取到的应用推送子任务。
在一个实施例中，服务器120在推送类型限制列表查询到提取到的推送信息类型时，判定应用推送任务为受推送限制的应用推送任务，需要根据历史推送记录对应用推送任务进行限制。服务器120根据提取到的推送信息类型和用户账号查询历史推送记录，根据查询到的历史推送记录统计各用户账号分别对应的已推送次数，从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号，根据筛选到的用户账号执行应用推送任务。
本实施例中，在推送类型限制列表中查询到应用推送任务的推送信息类型时，对查询到的推送信息类型对应的应用推送任务进行限制。通过推送信息类型列表设置需要控制的应用推送任务，提高应用推送任务的控制效率。 控制推送类型限制列表中推送信息类型对应的应用推送任务向同一用户账号的推送次数，避免用户账号多次接受到同一推送信息类型对应的推送信息。
如图5所示，在一个实施例中，S312之后具体还包括生成推送打扰提醒信息的步骤，该步骤具体包括以下内容：
S502，从提取到的用户账号中获取筛选后剩余的用户账号。
具体地，服务器120在从提取到的用户账号中筛选出已推送次数小于预设推送次数的用户账号后，获取提取到的用户账号中剩余的用户账号。
在一个实施例中，服务器120从提取到的用户账号中筛选出已推送次数大于等于预设推送次数的用户账号。
S504，根据获取到的用户账号生成推送打扰提醒信息。
具体地，服务器120提取获取到的用户账号对应的已推送次数，根据获取到的用户账号和获取到的用户账号各自对应的已推送次数，生成推送打扰提醒信息。例如，推送打扰提醒信息为“对用户账号A已经推送了N次；对用户账号B已经推送了M次”。
S506，将推送打扰提醒信息发送至以任务管理员账号登录的终端。
具体地，服务器120查询以任务管理员账号登录的终端120，将推送打扰提醒信息发送至查询到的终端110。终端110将推送打扰提醒信息展示在推送任务页面。
S508，接收以任务管理员账号登录的终端根据推送打扰提醒信息返回的强制推送指令。
具体地，终端110展示推送打扰提醒信息的推送任务页面中设置有强制推送按钮。推送管理员在查看推送打扰提醒信息后，决定要强制推送时，通过终端110的输入设备点击强制推送按钮。终端110检测到强制推送按钮被点击时，触发强制推送指令。终端110将强制推送指令发送至服务器120。
在一个实施例中，终端展示推送打扰提醒信息的推送任务页面中设置有放弃推送按钮。推送管理员在查看推送打扰提醒信息后，决定放弃对推送打 扰提醒信息对应的用户账号进行信息推送后，通过终端110的输入设备点击放弃推送按钮。终端110检测到放弃推送按钮被点击时，触发放弃推送指令，终端110将触发的放弃推送指令发送至服务器120。服务器120根据放弃推送指令放弃对获取到的用户账号进行信息推送。
S510，根据强制推送指令，以获取到的用户账号作为目标用户账号执行应用推送任务。
具体地，服务器120在接收到终端110返回的强制推送指令后，以获取到的用户账号作为应用推送任务的目标用户账号进行应用推送。
在一个实施例中，服务器120提取获取到的用户账号中的每个用户账号，分别以每个提取到的用户账号作为目标用户账号创建应用推送子任务，将创建的应用推送子任务添加到任务队列中。服务器120可按照预设读取数据从任务队列中读取应用推送子任务，并行执行读取到的应用推送子任务。
在一个实施例中，服务器120提取读取到的应用推送子任务中的推送信息和用户账号，查询登录有提取到的用户账号的终端，将提取到的推送信息发送至查询到的终端。
本实施例中，根据获取到的用户账号生成推送打扰提醒信息，将推送打扰提醒信息发用至以任务管理员账号登录的终端，以保证任务管理员可以根据打扰提醒信息决定是否对获取到的用户账号进行信息推送。
如图6所示，在一个实施例中，S510之后具体还包括更新历史推送记录的步骤，该步骤具体包括以下内容：
S602，提取已执行的应用推送任务对应的用户账号。
具体地，服务器120在执行完应用推送任务后，将应用推送任务标记为已执行。服务器120对已执行的应用推送任务进行解析，通过解析提取已执行的应用推送任务中的用户账号。
S604，判断提取到的用户账号是否为推送限制账号。
具体地，服务器120的数据库中存储着推送限制账号。服务器120在存 储的推送限制账号中查询提取到的用户账号，若在推送限制账号中查询到提取到的用户账号，则判定提取到的用户账号为推送限制账号。
S606，若判定提取到的用户账号为推送限制账号，提取已执行的应用推送任务中的推送信息类型。
具体地，服务器120在判定提取到的用户账号为推送限制账号时，对已执行的应用推送任务进行解析，通过解析提取已执行的应用推送任务中的推送信息类型。
S608，根据提取到的推送信息类型更新提取到的用户账号对应的历史推送记录。
具体地，服务器120查询提取到的用户账号和推送信息类型对应历史推送记录，对查询到的历史推送记录中的已推送次数进行更新。
在一个实施例中，服务器120获取已推送的应用推送任务的推送时间，将从获取到的推送时间、从已推送的应用推送任务中提取到的用户账号和推送信息类型对应存储作为历史推送记录。
在一个实施例中，应用推送方法具体还包括：接收以任务管理员账号登录的终端发送的推送限制名单配置指令；提取推送限制名单配置指令中的用户账号；根据提取到的用户账号创建推送用户限制名单。
S604具体包括：获取推送用户限制名单；根据推送用户限制名单判断提取到的用户账号是否为推送限制账号。
具体地，以任务管理员账号登录的终端110获取任务管理员输入的要配置为推送限制账号的用户账号，根据获取到的账号生成推送限制名单配置指令，将推送限制名单配置指令发送至服务器120。服务器120对推送限制名单配置指令进行解析，通过解析提取推送限制名单配置指令中的用户账号，根据提取到的用户账号创建推送用户限制名单。服务器120获取推送用户限制名单，根据推送用户限制名单中判断用户账号是否为推送限制账号。
本实施例中，在判定已执行的应用推送任务中的用户账号为推送限制账 号，根据从已执行的应用推送任务中推送信息类型更新用户账号对应的历史推送记录，保证历史推送记录的准确性，提高了根据历史推送记录筛选用户账号的准确性。
如图7所示，在一个实施例中，提供一种应用信息推送装置700，该装置具体包括以下内容：推送任务获取模块702、推送任务解析模块704、推送记录查询模块706、推送次数统计模块708、推送次数比较模块710和推送任务执行模块712。
推送任务获取模块702用于获取应用推送任务。推送任务解析模块704，用于提取应用推送任务中的推送信息类型和用户账号。推送记录查询模块706用于根据提取到的推送信息类型和用户账号查询历史推送记录。推送次数统计模块708用于根据查询到的历史推送记录统计各用户账号分别对应的已推送次数。推送次数比较模块710用于从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号。推送任务执行模块712用于根据筛选到的用户账号执行应用推送任务。
本实施例中，提取应用推送任务中推送信息类型和用户账号，查询与提取到的推送信息类型和用户账号对应的历史推送记录，根据历史记录统计各用户账号对应的推送次数，从提取到的用户账号中筛选统计到的推送次数小于预设推送次数的用户账号，根据筛选到的用户账号执行应用推送任务。根据推送次数筛选用户账号，可以保证筛选到的用户账号所对应用户为接收到与提取到的推送信息类型的推送信息的次数小于预设推送次数的用户，保证筛选到的用户账号所对应的用户不会频繁接收到同一推送信息类型的推送消息，从而也避免了筛选到的用户账号因为频繁接收到同一推送信息类型的推送消息而将应用卸载，导致避免了应用的用户数量减少的情况。
如图8所示，在一个实施例中，应用信息推送装置700具体还包括以下内容：限制列表获取模块714和信息类型查询模块716。
限制列表获取模块714，用于获取推送类型限制列表。信息类型查询模 块716，用于在推送类型限制列表中查询提取到的推送信息类型。推送任务执行模块712还用于若在推送类型限制列表中未查询到提取到的推送信息类型，判定应用推送任务为不受推送限制的应用推送任务，根据提取到的用户账号执行应用推送任务。推送记录查询模块706还用于若在推送类型限制列表中查询到提取到的推送信息类型，判定应用推送任务为受推送限制的应用推送任务，根据提取到的推送信息类型和用户账号查询历史推送记录。
本实施例中，在推送类型限制列表中查询到应用推送任务的推送信息类型时，对查询到的推送信息类型对应的应用推送任务进行限制。通过推送信息类型列表设置需要控制的应用推送任务，提高应用推送任务的控制效率。控制推送类型限制列表中推送信息类型对应的应用推送任务向同一用户账号的推送次数，避免用户账号多次接收到同一推送信息类型对应的推送信息。
如图9所示，在一个实施例中，应用信息推送装置700具体还包括以下内容：用户账号获取模块718、提醒信息生成模块720、提醒信息发送模块722和推送指令推送模块724。
用户账号获取模块718，用于从提取到的用户账号中获取筛选后剩余的用户账号。提醒信息生成模块720，用于根据获取到的用户账号生成推送打扰提醒信息。提醒信息发送模块722，用于将推送打扰提醒信息发送至以任务管理员账号登录的终端。推送指令推送模块724，用于接收以任务管理员账号登录的终端根据推送打扰提醒信息返回的强制推送指令。推送任务执行模块712还用于根据强制推送指令，以获取到的用户账号作为目标用户账号执行应用推送任务。
本实施例中，根据获取到的用户账号生成推送打扰提醒信息，将推送打扰提醒信息发用至以任务管理员账号登录的终端。从而提醒任务管理员可能对用户账号出现推送打扰的情况，以保证任务管理员可以根据打扰提醒信息决定是否对获取到的用户账号进行信息推送。
在一个实施例中，推送记录查询模块706还用于提取已执行的应用推送 任务对应的用户账号；判断提取到的用户账号是否为推送限制账号；若判定提取到的用户账号为推送限制账号，提取已执行的应用推送任务中的推送信息类型；根据提取到的推送信息类型更新提取到的用户账号对应的历史推送记录。判断提取到的用户账号是否为推送限制账号，包括：获取推送用户限制名单；根据推送用户限制名单判断提取到的用户账号是否为推送限制账号。
在一个实施例中，应用信息推送装置700具体还包括限制名单创建模块。限制名单创建模块，用于接收以任务管理员账号登录的终端发送的推送限制名单配置指令；提取推送限制名单配置指令中的用户账号；根据提取到的用户账号创建推送用户限制名单。
本实施例中，在判定已执行的应用推送任务中的用户账号为推送限制账号，根据从已执行的应用推送任务中推送信息类型更新用户账号对应的历史推送记录，保证历史推送记录的准确性，提高了根据历史推送记录筛选用户账号的准确性。
一种计算机设备，计算机设备包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，处理器执行计算机程序时实现以下步骤：获取应用推送任务；提取应用推送任务中的推送信息类型和用户账号；根据提取到的推送信息类型和用户账号查询历史推送记录；根据查询到的历史推送记录统计各用户账号分别对应的已推送次数；从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号；根据筛选到的用户账号执行应用推送任务。
在一个实施例中，提取应用推送任务中的推送信息类型和用户账号之后，处理器执行计算机程序时还实现以下步骤：获取推送类型限制列表；在推送类型限制列表中查询提取到的推送信息类型；若未查询到，则判定应用推送任务为不受推送限制的应用推送任务，根据提取到的用户账号执行应用推送任务；若查询到，则判定应用推送任务为受推送限制的应用推送任务，执行根据提取到的推送信息类型和用户账号查询历史推送记录的步骤。
在一个实施例中，根据筛选到的用户账号执行应用推送任务之后，处理器执行计算机程序时还实现以下步骤：从提取到的用户账号中获取筛选后剩余的用户账号；根据获取到的用户账号生成推送打扰提醒信息；将推送打扰提醒信息发送至以任务管理员账号登录的终端；接收以任务管理员账号登录的终端根据推送打扰提醒信息返回的强制推送指令；根据强制推送指令，以获取到的用户账号作为目标用户账号执行应用推送任务。
在一个实施例中，根据强制推送指令，以获取到的用户账号作为目标用户账号执行应用推送任务之后，处理器执行计算机程序时还实现以下步骤：提取已执行的应用推送任务对应的用户账号；判断提取到的用户账号是否为推送限制账号；若否，提取已执行的应用推送任务中的推送信息类型；根据提取到的推送信息类型更新提取到的用户账号对应的历史推送记录。
在一个实施例中，处理器执行计算机程序时还实现以下步骤：接收以任务管理员账号登录的终端发送的推送限制名单配置指令；提取推送限制名单配置指令中的用户账号；根据提取到的用户账号创建推送用户限制名单。判断提取到的用户账号是否为推送限制账号，包括：获取推送用户限制名单；根据推送用户限制名单判断提取到的用户账号是否为推送限制账号。
本实施例中，提取应用推送任务中推送信息类型和用户账号，查询与提取到的推送信息类型和用户账号对应的历史推送记录，根据历史记录统计各用户账号对应的推送次数，从提取到的用户账号中筛选统计到的推送次数小于预设推送次数的用户账号，根据筛选到的用户账号执行应用推送任务。根据推送次数筛选用户账号，可以保证筛选到的用户账号所对应用户为接收到与提取到的推送信息类型的推送信息的次数小于预设推送次数的用户，保证筛选到的用户账号所对应的用户不会频繁接收到同一推送信息类型的推送消息，从而也避免了筛选到的用户账号因为频繁接收到同一推送信息类型的推送消息而将应用卸载，导致避免了应用的用户数量减少的情况。
一个或多个存储有计算机可执行指令的存储介质，计算机可执行指令被 一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：获取应用推送任务；提取应用推送任务中的推送信息类型和用户账号；根据提取到的推送信息类型和用户账号查询历史推送记录；根据查询到的历史推送记录统计各用户账号分别对应的已推送次数；从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号；根据筛选到的用户账号执行应用推送任务
在一个实施例中，提取应用推送任务中的推送信息类型和用户账号之后，处理器执行计算机程序时还实现以下步骤：获取推送类型限制列表；在推送类型限制列表中查询提取到的推送信息类型；若未查询到，则判定应用推送任务为不受推送限制的应用推送任务，根据提取到的用户账号执行应用推送任务；若查询到，则判定应用推送任务为受推送限制的应用推送任务，执行根据提取到的推送信息类型和用户账号查询历史推送记录的步骤。
在一个实施例中，根据筛选到的用户账号执行应用推送任务之后，处理器还执行以下步骤：从提取到的用户账号中获取筛选后剩余的用户账号；根据获取到的用户账号生成推送打扰提醒信息；将推送打扰提醒信息发送至以任务管理员账号登录的终端；接收以任务管理员账号登录的终端根据推送打扰提醒信息返回的强制推送指令；根据强制推送指令，以获取到的用户账号作为目标用户账号执行应用推送任务。
在一个实施例中，根据强制推送指令，以获取到的用户账号作为目标用户账号执行应用推送任务之后，处理器还执行以下步骤：提取已执行的应用推送任务对应的用户账号；判断提取到的用户账号是否为推送限制账号；若否，提取已执行的应用推送任务中的推送信息类型；根据提取到的推送信息类型更新提取到的用户账号对应的历史推送记录。
在一个实施例中，处理器还执行以下步骤：接收以任务管理员账号登录的终端发送的推送限制名单配置指令；提取推送限制名单配置指令中的用户账号；根据提取到的用户账号创建推送用户限制名单。
本实施例中，提取应用推送任务中推送信息类型和用户账号，查询与提取到的推送信息类型和用户账号对应的历史推送记录，根据历史记录统计各用户账号对应的推送次数，从提取到的用户账号中筛选统计到的推送次数小于预设推送次数的用户账号，根据筛选到的用户账号执行应用推送任务。根据推送次数筛选用户账号，可以保证筛选到的用户账号所对应用户为接收到与提取到的推送信息类型的推送信息的次数小于预设推送次数的用户，保证筛选到的用户账号所对应的用户不会频繁接收到同一推送信息类型的推送消息，从而也避免了筛选到的用户账号因为频繁接收到同一推送信息类型的推送消息而将应用卸载，导致避免了应用的用户数量减少的情况。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，该计算机程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，前述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)等非易失性存储介质，或随机存储记忆体(Random Access Memory，RAM)等。
以上所述实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (18)

  1. 一种应用信息推送方法，所述方法包括：获取应用推送任务；提取所述应用推送任务中的推送信息类型和用户账号；根据提取到的推送信息类型和用户账号查询历史推送记录；根据查询到的历史推送记录统计各用户账号分别对应的已推送次数；从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号；根据筛选到的用户账号执行所述应用推送任务。
  2. 根据权利要求1所述的方法，其特征在于，所述提取所述应用推送任务中的推送信息类型和用户账号之后，还包括：获取推送类型限制列表；在所述推送类型限制列表中查询提取到的推送信息类型；若未查询到，则判定所述应用推送任务为不受推送限制的应用推送任务，根据提取到的用户账号执行所述应用推送任务；若查询到，则判定所述应用推送任务为受推送限制的应用推送任务，执行所述根据提取到的推送信息类型和用户账号查询历史推送记录的步骤。
  3. 根据权利要求1所述的方法，其特征在于，所述根据筛选到的用户账号执行所述应用推送任务之后，还包括：从所述提取到的用户账号中获取筛选后剩余的用户账号；根据获取到的用户账号生成推送打扰提醒信息；将所述推送打扰提醒信息发送至以任务管理员账号登录的终端；接收所述以任务管理员账号登录的终端根据所述推送打扰提醒信息返回的强制推送指令；根据所述强制推送指令，以所述获取到的用户账号作为目标用户账号执行所述应用推送任务。
  4. 根据权利要求3所述的方法，其特征在于，所述根据所述强制推送指令，以所述获取到的用户账号作为目标用户账号执行所述应用推送任务之后，还包括：提取已执行的应用推送任务对应的用户账号；判断提取到的用户账号是否为推送限制账号；若否，提取所述已执行的应用推送任务中的推送信息类型；根据所述提取到的推送信息类型更新所述提取到的用户账号对 应的历史推送记录。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：接收以任务管理员账号登录的终端发送的推送限制名单配置指令；提取所述推送限制名单配置指令中的用户账号；根据提取到的用户账号创建推送用户限制名单；所述判断提取到的用户账号是否为推送限制账号，包括：获取推送用户限制名单；根据所述推送用户限制名单判断提取到的用户账号是否为推送限制账号。
  6. 一种应用信息推送装置，其特征在于，所述装置包括：推送任务获取模块，用于获取应用推送任务；推送任务解析模块，用于提取所述应用推送任务中的推送信息类型和用户账号；推送记录查询模块，用于根据提取到的推送信息类型和用户账号查询历史推送记录；推送次数统计模块，用于根据查询到的历史推送记录统计各用户账号分别对应的已推送次数；推送次数比较模块，用于从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号；推送任务执行模块，用于根据筛选到的用户账号执行所述应用推送任务。
  7. 根据权利要求6所述的装置，其特征在于，所述装置还包括：限制列表获取模块，用于获取推送类型限制列表；信息类型查询模块，用于在所述推送类型限制列表中查询提取到的推送信息类型；所述推送任务执行模块还用于若在所述推送类型限制列表中未查询到提取到的推送信息类型，判定所述应用推送任务为不受推送限制的应用推送任务，根据提取到的用户账号执行所述应用推送任务；所述推送记录查询模块还用于若在所述推送类型限制列表中查询到提取到的推送信息类型，判定所述应用推送任务为受推送限制的应用推送任务，根据提取到的推送信息类型和用户账号查询历史推送记录。
  8. 根据权利要求6所述的装置，其特征在于，所述装置还包括：用户账号获取模块，用于从所述提取到的用户账号中获取筛选后剩余的用户账号； 提醒信息生成模块，用于根据获取到的用户账号生成推送打扰提醒信息；提醒信息发送模块，用于将所述推送打扰提醒信息发送至以任务管理员账号登录的终端；推送指令推送模块，用于接收所述以任务管理员账号登录的终端根据所述推送打扰提醒信息返回的强制推送指令；所述推送任务执行模块还用于根据所述强制推送指令，以所述获取到的用户账号作为目标用户账号执行所述应用推送任务。
  9. 一种计算机设备，所述计算机设备包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现以下步骤：获取应用推送任务；提取所述应用推送任务中的推送信息类型和用户账号；根据提取到的推送信息类型和用户账号查询历史推送记录；根据查询到的历史推送记录统计各用户账号分别对应的已推送次数；从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号；根据筛选到的用户账号执行所述应用推送任务。
  10. 根据权利要求9所述的计算机设备，其特征在于，所述提取所述应用推送任务中的推送信息类型和用户账号之后，还包括：获取推送类型限制列表；在所述推送类型限制列表中查询提取到的推送信息类型；若未查询到，则判定所述应用推送任务为不受推送限制的应用推送任务，根据提取到的用户账号执行所述应用推送任务；若查询到，则判定所述应用推送任务为受推送限制的应用推送任务，执行所述根据提取到的推送信息类型和用户账号查询历史推送记录的步骤。
  11. 根据权利要求9所述的计算机设备，其特征在于，所述根据筛选到的用户账号执行所述应用推送任务之后，还包括：从所述提取到的用户账号中获取筛选后剩余的用户账号；根据获取到的用户账号生成推送打扰提醒信息；将所述推送打扰提醒信息发送至以任务管理员账号登录的终端；接收所述以任务管理员账号登录的终端根据所述推送打扰提醒信息返回的强制推送指令；根据所述强制推送指令，以所述获取到的用户账号作为目标用户账 号执行所述应用推送任务。
  12. 根据权利要求11所述的计算机设备，其特征在于，所述根据所述强制推送指令，以所述获取到的用户账号作为目标用户账号执行所述应用推送任务之后，还包括：提取已执行的应用推送任务对应的用户账号；判断提取到的用户账号是否为推送限制账号；若否，提取所述已执行的应用推送任务中的推送信息类型；根据所述提取到的推送信息类型更新所述提取到的用户账号对应的历史推送记录。
  13. 根据权利要求12所述的计算机设备，其特征在于，所述处理器执行所述计算机程序时还实现以下步骤：接收以任务管理员账号登录的终端发送的推送限制名单配置指令；提取所述推送限制名单配置指令中的用户账号；根据提取到的用户账号创建推送用户限制名单；所述判断提取到的用户账号是否为推送限制账号，包括：获取推送用户限制名单；根据所述推送用户限制名单判断提取到的用户账号是否为推送限制账号。
  14. 一个或多个存储有计算机可执行指令的存储介质，所述计算机可执行指令被一个或多个处理器执行时，使得所述一个或多个处理器执行以下步骤：获取应用推送任务；提取所述应用推送任务中的推送信息类型和用户账号；根据提取到的推送信息类型和用户账号查询历史推送记录；根据查询到的历史推送记录统计各用户账号分别对应的已推送次数；从提取到的用户账号中筛选统计的已推送次数小于预设推送次数的用户账号；根据筛选到的用户账号执行所述应用推送任务。
  15. 根据权利要求14所述的存储介质，其特征在于，所述提取所述应用推送任务中的推送信息类型和用户账号之后，还包括：获取推送类型限制列表；在所述推送类型限制列表中查询提取到的推送信息类型；若未查询到，则判定所述应用推送任务为不受推送限制的应用推送任务，根据提取到的用户账号执行所述应用推送任务；若查询到，则判定所述应用推送任务为受推送限制的应用推送任务，执行所述根据提取到的推送信息类型和用户账号查 询历史推送记录的步骤。
  16. 根据权利要求14所述的存储介质，其特征在于，所述根据筛选到的用户账号执行所述应用推送任务之后，还包括：从所述提取到的用户账号中获取筛选后剩余的用户账号；根据获取到的用户账号生成推送打扰提醒信息；将所述推送打扰提醒信息发送至以任务管理员账号登录的终端；接收所述以任务管理员账号登录的终端根据所述推送打扰提醒信息返回的强制推送指令；根据所述强制推送指令，以所述获取到的用户账号作为目标用户账号执行所述应用推送任务。
  17. 根据权利要求16所述的存储介质，其特征在于，所述根据所述强制推送指令，以所述获取到的用户账号作为目标用户账号执行所述应用推送任务之后，还包括：提取已执行的应用推送任务对应的用户账号；判断提取到的用户账号是否为推送限制账号；若否，提取所述已执行的应用推送任务中的推送信息类型；根据所述提取到的推送信息类型更新所述提取到的用户账号对应的历史推送记录。
  18. 根据权利要求17所述的存储介质，其特征在于，一个或多个处理器还执行以下步骤：接收以任务管理员账号登录的终端发送的推送限制名单配置指令；提取所述推送限制名单配置指令中的用户账号；根据提取到的用户账号创建推送用户限制名单；所述判断提取到的用户账号是否为推送限制账号，包括：获取推送用户限制名单；根据所述推送用户限制名单判断提取到的用户账号是否为推送限制账号。
PCT/CN2018/078312 2017-07-24 2018-03-07 应用信息推送方法、装置、计算机设备和存储介质 WO2019019642A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710608519.1 2017-07-24
CN201710608519.1A CN107733968B (zh) 2017-07-24 2017-07-24 应用信息推送方法、装置、计算机设备和存储介质

Publications (1)

Publication Number Publication Date
WO2019019642A1 true WO2019019642A1 (zh) 2019-01-31

Family

ID=61201296

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/078312 WO2019019642A1 (zh) 2017-07-24 2018-03-07 应用信息推送方法、装置、计算机设备和存储介质

Country Status (2)

Country Link
CN (1) CN107733968B (zh)
WO (1) WO2019019642A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110490651A (zh) * 2019-08-14 2019-11-22 平安科技（深圳）有限公司 信息推送方法、装置、设备及计算机可读存储介质
CN110751168A (zh) * 2019-09-03 2020-02-04 深圳壹账通智能科技有限公司 信息推送方法、装置、计算机设备和存储介质
WO2020199750A1 (zh) * 2019-04-04 2020-10-08 北京字节跳动网络技术有限公司 基于历史记录的信息推送方法、装置及电子设备
CN113362095A (zh) * 2020-03-05 2021-09-07 北京沃东天骏信息技术有限公司 一种信息投放的方法和装置
CN114363408A (zh) * 2021-12-31 2022-04-15 北京金堤科技有限公司 信息推送方法、装置、计算机可读介质及计算机设备

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107733968B (zh) * 2017-07-24 2020-05-29 深圳壹账通智能科技有限公司 应用信息推送方法、装置、计算机设备和存储介质
CN110619534A (zh) * 2018-06-19 2019-12-27 华为技术有限公司 一种营销信息推送方法、装置及可读存储介质
CN109636475A (zh) * 2018-12-14 2019-04-16 平安城市建设科技(深圳)有限公司 房源刷新方法、装置、设备及存储介质
CN110708360A (zh) * 2019-09-17 2020-01-17 Oppo广东移动通信有限公司 一种信息处理方法、系统和电子设备
CN112380266A (zh) * 2020-10-16 2021-02-19 广州市百果园网络科技有限公司 消息数据处理方法、装置、设备和存储介质
CN112804134B (zh) * 2020-12-31 2022-10-04 深圳市镜玩科技有限公司 基于即时通信的任务发起方法、相关装置、设备及介质
CN114115654A (zh) * 2021-10-29 2022-03-01 北京蓝莓时节科技有限公司 提升用户内容创作率的方法、装置、系统和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103327110A (zh) * 2013-06-28 2013-09-25 腾讯科技（深圳）有限公司 一种信息推送方法和系统
CN104980327A (zh) * 2014-04-03 2015-10-14 腾讯科技（深圳）有限公司 一种消息推送方法及装置
CN105847447A (zh) * 2016-06-01 2016-08-10 腾讯科技（深圳）有限公司 消息推送方法和装置
US20170048343A1 (en) * 2012-06-22 2017-02-16 Salesforce.Com, Inc. Methods and systems for priority-based notifications for mobile devices
CN107733968A (zh) * 2017-07-24 2018-02-23 上海壹账通金融科技有限公司 应用信息推送方法、装置、计算机设备和存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104216921B (zh) * 2013-06-05 2019-06-04 腾讯科技（深圳）有限公司 一种实现浏览器中快速链接的添加提示方法、装置及系统
CN104717616A (zh) * 2013-12-13 2015-06-17 腾讯科技（深圳）有限公司 一种推送消息的管理方法及装置
CN105589877B (zh) * 2014-10-23 2020-05-22 腾讯科技（深圳）有限公司 信息推送方法及应用平台
CN104735150A (zh) * 2015-03-27 2015-06-24 努比亚技术有限公司 消息推送方法和装置
CN105511876B (zh) * 2015-12-04 2019-05-03 Oppo广东移动通信有限公司 一种推送信息的处理方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170048343A1 (en) * 2012-06-22 2017-02-16 Salesforce.Com, Inc. Methods and systems for priority-based notifications for mobile devices
CN103327110A (zh) * 2013-06-28 2013-09-25 腾讯科技（深圳）有限公司 一种信息推送方法和系统
CN104980327A (zh) * 2014-04-03 2015-10-14 腾讯科技（深圳）有限公司 一种消息推送方法及装置
CN105847447A (zh) * 2016-06-01 2016-08-10 腾讯科技（深圳）有限公司 消息推送方法和装置
CN107733968A (zh) * 2017-07-24 2018-02-23 上海壹账通金融科技有限公司 应用信息推送方法、装置、计算机设备和存储介质

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020199750A1 (zh) * 2019-04-04 2020-10-08 北京字节跳动网络技术有限公司 基于历史记录的信息推送方法、装置及电子设备
CN110490651A (zh) * 2019-08-14 2019-11-22 平安科技（深圳）有限公司 信息推送方法、装置、设备及计算机可读存储介质
CN110490651B (zh) * 2019-08-14 2023-11-14 平安科技（深圳）有限公司 信息推送方法、装置、设备及计算机可读存储介质
CN110751168A (zh) * 2019-09-03 2020-02-04 深圳壹账通智能科技有限公司 信息推送方法、装置、计算机设备和存储介质
CN113362095A (zh) * 2020-03-05 2021-09-07 北京沃东天骏信息技术有限公司 一种信息投放的方法和装置
CN114363408A (zh) * 2021-12-31 2022-04-15 北京金堤科技有限公司 信息推送方法、装置、计算机可读介质及计算机设备

Also Published As

Publication number Publication date
CN107733968A (zh) 2018-02-23
CN107733968B (zh) 2020-05-29

Similar Documents

Publication Publication Date Title
WO2019019642A1 (zh) 应用信息推送方法、装置、计算机设备和存储介质
JP6629697B2 (ja) 仮想マシンイメージファイルを抽出する方法および装置
US10380103B2 (en) Object data updating method and apparatus in an object storage system
JP5007339B2 (ja) ウェブシンジケーションを介した双方向マルチマスタ同期
US20080072225A1 (en) Information processing apparatus, information processing method, program, and recording medium
US9355250B2 (en) Method and system for rapidly scanning files
US9514291B2 (en) Information processing system, information processing device, and authentication information management method
WO2019019670A1 (zh) 应用访问方法、装置、计算机设备和存储介质
US10021050B2 (en) Secure conversation and document binder
US11153071B2 (en) Citation and attribution management methods and systems
US10747728B2 (en) Edit and share unsupported files through instantly generated preview
EP2977917A1 (en) Ensuring consistency of derived data in a distributed storage system
US20160283447A1 (en) Providing interactive preview of content within communication
US11841842B2 (en) Method and system for using external content type object types
US20200327161A1 (en) Video processing method, device, terminal and storage medium
US11625305B2 (en) Method and system for indexing fragmented user data objects
US9286055B1 (en) System, method, and computer program for aggregating fragments of data objects from a plurality of devices
US8510346B2 (en) Efficiently handling information on changes to a UDDI registry including those resulting in virtual deletes
US11729130B2 (en) Live database records in a chat platform
CN108073638B (zh) 数据诊断方法及装置
CN115001967A (zh) 一种数据采集方法、装置、电子设备及存储介质
CN114239510A (zh) 业务信息的处理方法、装置、存储介质和电子设备
CN110781142B (zh) 数据导入方法及装置、服务端及存储介质
US9465876B2 (en) Managing content available for content prediction
TWI531910B (zh) 資料管理方法、電腦程式產品及管理伺服器端

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18838594

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18838594

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 28/05/2020)