WO2020181812A1

WO2020181812A1 - Application broadcast message push method, apparatus, and readable storage medium

Info

Publication number: WO2020181812A1
Application number: PCT/CN2019/117727
Authority: WO
Inventors: 乐志能
Original assignee: 平安科技（深圳）有限公司
Priority date: 2019-03-11
Filing date: 2019-11-13
Publication date: 2020-09-17
Also published as: CN109889349A; CN109889349B

Abstract

The present application provides an application broadcast message push method, apparatus, and readable storage medium, said method comprising: for any target application, searching in a database for a device ID associated with said target application, and storing each of the found device IDs in at least one device information file corresponding to the target application; receiving a broadcast message push instruction for the target application; pushing the instruction according to said broadcast message, and obtaining at least one of said device information files corresponding to the target application; according to the device ID stored in each of the obtained device information files, pushing the broadcast message to a mobile phone device corresponding to the device ID. The apparatus comprises: a storage module, a receiving module, an obtaining module, and a push module. The present solution improves the efficiency of pushing broadcast messages to users by means of an application.

Description

APP broadcast message pushing method, device and readable storage medium

This application claims the priority of the Chinese patent application filed on March 11, 2019 with the Chinese Patent Office, the application number is 2019101820585, and the application name is "A method, device and readable storage medium for APP broadcast message push", and its entire contents Incorporated in the application by reference.

Technical field

This application relates to the field of communication technology, and in particular to an APP broadcast message pushing method, device and readable storage medium.

Background technique

As mobile phones become more intelligent, mobile phones are no longer simple communication tools. Users can install various types of APP (Application, mobile phone software) on their phones, and use APPs for social networking, shopping, sports, games, and movies. Watch and other activities. At the same time, in order to achieve the purposes of promoting products, improving user experience, maintaining existing users, and developing new users, operators of various types of APP will push broadcast messages to users through APP, that is, to mobile devices with specific APPs. Push broadcast messages on. At present, when pushing broadcast messages to users through APPs, it is first necessary to determine the target APP to which the broadcast message is pushed, and then find the device ID associated with the target APP from the database, and then according to the found device ID to install the target APP mobile devices push broadcast messages. The inventor found that because the same APP operator may have multiple APPs, and the association relationships between different APPs and device IDs are all stored in the same database, the amount of data on the association relationship between APPs and device IDs stored in the database is relatively large. It takes a long time to find the device ID that is associated with the target APP, which in turn leads to low efficiency in pushing broadcast messages to users through the APP.

Summary of the invention

This application provides an APP broadcast message pushing method, device, and readable storage medium. Each device ID associated with the same APP is stored in one or more device information files in advance. After receiving the broadcast message for the APP After the push instruction, directly push the broadcast message to the corresponding mobile phone device according to the device ID stored in each device information file corresponding to the APP, without temporarily searching the database for the device associated with the APP after receiving the broadcast message push instruction ID, which can improve the efficiency of pushing broadcast messages to users through APP.

In the first aspect, an embodiment of the present application provides an APP broadcast message push method, which includes: for any target APP, searching a database for the device ID associated with the target APP, and combining each of the found devices The ID is stored in at least one device information file corresponding to the target APP to receive a broadcast message push instruction for the target APP; according to the broadcast message push instruction, at least one of the device information files corresponding to the target APP is obtained Device information file; according to the device ID stored in each acquired device information file, push a broadcast message to the mobile phone device corresponding to the device ID, including: for each acquired device information The file creates a corresponding message push thread; at the same time, each of the created message push threads is run, so that each message push thread sends a message to the device ID stored in the corresponding device information file. The corresponding mobile phone device pushes the broadcast message.

In the second aspect, this application also provides an APP broadcast message pushing device, including: a storage module, a receiving module, an acquisition module, and a pushing module;

The storage module is configured to search for a device ID associated with the target APP from a database for any target APP, and store each of the device IDs found in at least one corresponding to the target APP In the equipment information file;

The receiving module is configured to receive a broadcast message push instruction for the target APP;

The obtaining module is configured to obtain at least one of the device information files generated by the storage module and corresponding to the target APP according to the broadcast message push instruction received by the receiving module;

The pushing module is configured to push a broadcast message to the mobile phone device corresponding to the device ID according to the device ID stored in each device information file acquired by the acquisition module;

The push module is specifically configured to create a corresponding message push thread for each acquired device information file; at the same time, run each of the created message push threads to make each message push thread Push a broadcast message to the corresponding mobile phone device according to the device ID stored in the corresponding device information file.

In a third aspect, an embodiment of the present application also provides a computer device, including a memory and a processor, the memory stores computer-readable instructions, and when the processor executes the computer-readable instructions, the foregoing first aspect is implemented Any of the aforementioned APP broadcast message push methods.

In a fourth aspect, an embodiment of the present application also provides a non-volatile readable storage medium, on which computer-readable instructions are stored, and when the computer-readable instructions are executed by a processor, any one of the above-mentioned first aspects is implemented. The APP broadcast message push method.

The APP broadcast message pushing method, device, computer equipment, and computer-readable storage medium provided by the embodiments of the application store each device ID associated with the target APP stored in the database in one or more corresponding to the target APP in advance. In the device information file, after receiving the broadcast message push instruction for the target APP, each device information file corresponding to the target APP is obtained, and then the device ID stored in each obtained device information file is sent to the corresponding mobile device Push broadcast messages. It can be seen that each device ID associated with the same APP is stored in one or more device information files in advance, and after receiving the broadcast message push instruction for the APP, it is directly based on the device information files corresponding to the APP. The device ID stored in the device pushes the broadcast message to the corresponding mobile device. There is no need to temporarily find the device ID associated with the APP from the database after receiving the broadcast message push instruction, thereby improving the efficiency of pushing broadcast messages to users through the APP .

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are For some of the embodiments of the application, for those of ordinary skill in the art, other drawings may be obtained based on these drawings without creative work.

FIG. 1 is a flowchart of an APP broadcast message push method provided by an embodiment of the present application;

2 is a flowchart of a method for determining the number of required device information files provided by an embodiment of the present application;

FIG. 3 is a flowchart of a device ID storage method provided by an embodiment of the present application;

FIG. 4 is a flowchart of a method for updating a device information file provided by an embodiment of the present application;

FIG. 5 is a flowchart of another method for pushing APP broadcast messages according to an embodiment of the present application;

Fig. 6 is a schematic diagram of an APP broadcast message pushing device provided by an embodiment of the present application.

detailed description

In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments These are part of the embodiments of this application, not all of them. Based on the examples of this application, all other embodiments obtained by those of ordinary skill in the art without creative work are protected by this application. range. It should be understood that the specific embodiments described herein are only used to explain the application, but not used to limit the application.

As shown in Figure 1, an embodiment of the present application provides a method for pushing APP broadcast messages. The method may include the following steps:

Step 101: For any target APP, search the database for the device ID associated with the target APP, and store each of the found device IDs in at least one device information file corresponding to the target APP;

Step 102: Receive a broadcast message push instruction for the target APP;

Step 103: Obtain at least one device information file corresponding to the target APP according to the broadcast message push instruction;

Step 104: Push the broadcast message to the mobile phone device corresponding to the device ID according to the device ID stored in each device information file obtained.

The APP broadcast message push method provided by the embodiment of the present application pre-stores each device ID stored in the database and associated with the target APP into one or more device information files corresponding to the target APP. After the broadcast message push instruction, obtain each device information file corresponding to the target APP, and then push the broadcast message to the corresponding mobile device according to the device ID stored in each obtained device information file. It can be seen that each device ID associated with the same APP is stored in one or more device information files in advance, and after receiving the broadcast message push instruction for the APP, it is directly based on the device information files corresponding to the APP. The device ID stored in the device pushes the broadcast message to the corresponding mobile device. There is no need to temporarily find the device ID associated with the APP from the database after receiving the broadcast message push instruction, thereby improving the efficiency of pushing broadcast messages to users through the APP . In the embodiment of the present application, the device ID associated with the APP is stored in the database. The same APP can be associated with multiple device IDs, and the same device ID can also be associated with multiple APPs. For any APP, the device ID associated with the APP refers to the identity of the mobile device on which the APP is installed. Different mobile devices have different device IDs (identifications), and a corresponding mobile phone can be uniquely determined according to the device ID Device, so that information can be accurately sent to the corresponding mobile device according to the device ID. In addition, the database stores the association relationship between the APP and the device ID. When the mobile device runs the corresponding APP for the first time, the APP can upload the device ID of the mobile device, and then can create the association relationship between the APP and the device ID according to the device ID uploaded by the APP. Store the created relationship in the database.

In addition, when the broadcast message is pushed to the corresponding mobile phone device according to the device ID in the device information file, the content of the pushed broadcast message can be obtained from the broadcast message push instruction.

Optionally, based on the APP broadcast message push method shown in FIG. 1, when step 104 pushes the broadcast message to the mobile device according to the device information file, multiple threads can be used to push the broadcast message at the same time. The specific process can be implemented as follows :

For each device information file obtained, create a message push thread corresponding to the device information file; at the same time, run each message push thread created so that each message push thread can be based on its corresponding device The device ID stored in the information file pushes the broadcast message to the corresponding mobile device. For example, if a total of 10 device information files corresponding to the target APP are obtained, 10 message push threads are created, so that each device information file can independently correspond to a message push thread. After that, 10 message push threads are made in parallel, and each message push thread can read the device ID from its corresponding device information file in sequence during operation, and then send the corresponding mobile device to the corresponding mobile device according to the read device ID. Push broadcast messages. Create a corresponding message push thread for each acquired device information file, and run the created message push threads at the same time, so that each message push thread can simultaneously send messages to the mobile device according to the device ID in the corresponding device information file Push broadcast messages, so that broadcast messages can be pushed to multiple mobile devices at the same time, which further improves the efficiency of pushing broadcast messages to users through APP.

Optionally, based on the APP broadcast message push method shown in FIG. 1, before storing each found device ID in the device information file corresponding to the target APP, a certain number of device information files need to be created first. As shown in Figure 2, the process of creating a device information file may specifically include the following steps:

Step 201: Obtain the number of device IDs associated with the target APP found in the database;

Step 202: Substitute the acquired number of device IDs into the following formula to calculate the number of required device information files;

In the above formula, M represents the number of required device information files; x represents the number of device IDs found in the database and associated with the target APP; X represents a preset number threshold; m represents a broadcast The maximum number of message push threads that a message push device can run; k represents a constant determined according to the maximum number of device IDs that can be stored in a device information file;

Step 203: Create a corresponding number of device information files according to the calculated number of required device information files.

In the embodiment of this application, pushing broadcast messages to mobile devices needs to rely on broadcast message push devices, and the number of message push threads that each broadcast message push device can support is limited by the maximum value. When a thread pushes a broadcast message to a mobile phone device, each message push thread corresponds to a device information file, and different message push threads correspond to different device information files. Therefore, it is necessary to determine the number of required device information files according to the number of acquired device IDs, so as to ensure that the broadcast message pushing device has a high utilization rate while ensuring the efficiency of pushing broadcast messages. When the number x of the device IDs found is less than the preset number threshold X, directly create a fixed number (m) of device information files as the device information files corresponding to the target APP, and m is a broadcast message The maximum number of message push threads that the push device can run, so that it has a higher message push efficiency under the premise of only using one broadcast message push device. When the number x of the device IDs found is greater than or equal to the preset number threshold X, it will be determined according to the number x of the device IDs found and the maximum number of device IDs that can be stored in a device information file. Determine the constant k, calculate the number of device information files that need to be created

Ensure that each device information file created can store all the device IDs found. among them,

And

Refers to the ratio of x to k rounded up.

In the above formula, the preset number threshold X can be equal to or less than the product of the maximum number of device IDs that can be stored in a device information file and m. At this time, it can avoid storing the device ID in the device information file. The device information files are all in a fully loaded state, ensuring that each device information file created can store each device ID found. In addition, the constant k can be equal to or less than the maximum number of device IDs that can be stored in a device information file. When k is less than the maximum number of device IDs that can be stored in a device information file, each device information file will not be in Fully loaded state. When the number of queried device IDs associated with the target APP is small, create a fixed number of device information files to store the queried device IDs, so that a broadcast message push device can run simultaneously with each device separately Multiple message push threads corresponding to the information file perform broadcast message push, which avoids resource waste caused by enabling multiple broadcast message push devices while ensuring the efficiency of broadcast message push. When the number of device IDs associated with the target APP is large, multiple device information files are created according to actual needs to store the queried device IDs, and then multiple message push threads are run simultaneously through multiple broadcast message push devices Carry out broadcast message push to ensure the efficiency of broadcast message push.

Optionally, based on the APP broadcast message push method shown in FIG. 1, when storing the found device ID in the device information file in step 101, each device ID may be stored in the corresponding device ID according to the priority of each device ID. In the device information file. As shown in FIG. 3, the method of storing the device ID in the device information file may specifically include the following steps:

Step 301: Perform statistics on the priority of each device ID found, and determine the priority distribution information of each device ID found;

Step 302: According to the determined priority distribution information, each device information file device corresponds to the priority file ratio;

Step 303: According to the priority of each device ID found and the proportion of priority files corresponding to each device information file, store each device ID found in each device information file, so that each device information file is different The proportion of the priority device ID conforms to the proportion of the priority file corresponding to the device information file.

In this embodiment of the application, each device ID associated with the target APP found in the database has a corresponding priority. By counting the priority of each device ID found, it can be determined that the device ID found The priority distribution information of each device ID, that is, the number of device IDs corresponding to each priority. After the priority distribution information of the device ID is determined, the corresponding priority file ratio can be set for each device information file according to the priority distribution information, that is, the device information file can be set for each priority device The number of IDs. Then, according to the priority of each device ID and the corresponding priority proportion of each device information file, each device ID is stored in each device information file, and the number of device IDs with different priorities in each device information file is guaranteed after the storage is completed. The proportion of files that meet the corresponding priority. For example, a total of 3 device information files are created for the target APP, namely device information file 1, device information file 2 and device information file 3. According to the priority distribution information obtained by statistical analysis of the priority of the device ID, The priority file proportion of device information file 1 is set to high priority: medium priority: low priority = 1:0:0, and the priority file proportion of device information file 2 is set to high priority: medium priority : Low priority=0.7:0.3:0, set the priority file ratio of device information file 3 to high priority: medium priority: low priority=0:0.4:0.6. Then, according to the proportion of the priority files corresponding to each of the three device information files, each of the found device IDs is allocated to the three device information files for storage. After the storage is complete, the device information file 1 contains all high-priority device IDs; the device information file 2 only includes high-priority and medium-priority device IDs, and high-priority device IDs and medium-priority device IDs The number ratio of is equal to 0.7:0.3; the device information file 3 only includes medium priority and low priority device IDs, and the number ratio of medium priority device IDs to low priority device IDs is equal to 0.4:0.6. Store each device ID in each device information file according to the proportion of priority files corresponding to each device information file. When pushing broadcast messages to mobile devices according to the device ID stored in the device information file, for each device information file, you can Push the broadcast message to the corresponding mobile device according to the priority order of the device ID in the device information file, and push the broadcast message to the mobile device with the higher priority of the device ID first, and realize the push of the broadcast message to the mobile device in stages, which improves Applicability of the APP broadcast message push method.

In addition, the proportion of priority files corresponding to different device information files can be different. When you need to push broadcast messages to mobile devices with a specific priority device ID, you only need to determine the proportion of the corresponding priority files that the specific priority is not The zero device information file is read, and then broadcast messages are pushed to the mobile device according to the read priority of the device ID of the specific priority, so that the broadcast message can be easily pushed to the mobile device of the specific priority device ID to meet The individual needs of different users. It should be noted that the priority of the device ID can be set when the device ID is stored in the database, or can be set according to the user's instruction after the device ID is found in the database.

Optionally, based on the APP broadcast message push method shown in FIG. 1, after step 101 stores the found device ID in the device information file, the device ID associated with the target APP can be added to the database. It is also stored in the device information file, as shown in Figure 4. The specific process may include the following steps:

Step 401: After a preset update period, search the database for the newly added device ID associated with the target APP, where the newly added device ID refers to the device ID added to the database during the update period;

Step 402: Create at least one newly added device information file corresponding to the target APP;

Step 403: Store the newly found device ID in at least one newly created device information file.

After searching for the device ID associated with the target APP from the database for the first time, and storing the found device ID in the device information file corresponding to the target APP, there may be new devices associated with the target APP in the database ID, in order to push the broadcast message to the mobile device corresponding to the newly added device ID when the broadcast message is pushed for the target APP, the newly added device ID associated with the target APP in the database needs to be also stored in the device information file. To this end, after each update cycle, the database is searched for the newly added device ID associated with the target APP, and one or more device information files corresponding to the target APP are newly created to store the newly found device ID. . After each update cycle, search the database for the newly added device IDs that are added to the database during the update cycle and are associated with the target APP, and store the found new device IDs in the newly created new device information file After that, the new device information file will be stored together with the previously generated device information file corresponding to the target APP. When the broadcast message needs to be pushed to the target APP again, it will also be sent to the device according to the device ID stored in the new device information file. The mobile device pushes the broadcast message, so as to ensure that the push broadcast message can cover all mobile devices with the target APP installed, and improve the comprehensiveness of the push broadcast message.

It should be noted that the database needs to be traversed when looking up the new device ID from the database, which will take up more computing resources. In order to avoid finding the new device ID affecting the normal access to the database, you can search for the new device in the free time of the database. Device ID. For example, you can start to query the newly added device ID in the database at one o'clock every morning.

Optionally, on the basis of the method of storing the ID of the newly added device shown in FIG. 4, after finding the ID of the newly added device associated with the target APP from the database in step 401, the ID of each newly added device that is found can be configured separately priority. After configuring the priority for the new device ID and storing the new device ID in the new device information file, when you need to push broadcast messages for mobile devices with a specific priority device ID, you can use the new device information file The device ID with a specific priority pushes the broadcast message to the corresponding mobile device, so as to ensure that all mobile devices with the specific priority can be covered when the broadcast message is pushed to the mobile device with a specific priority, thereby ensuring that the broadcast message is pushed Comprehensiveness.

Optionally, based on the method of storing the ID of the newly added device shown in FIG. 4, all newly added device files formed during the integration period may be integrated. Specifically, every time a preset integration period is passed, each new device information file corresponding to the target APP created in the integration period is queried, and then the new device information stored in each new device information file found The ID is integrated into one or more device information files, and then each newly added device information file found is deleted. Since each update cycle may generate one or more new device information files corresponding to the target APP, many new device information files with a small number of stored device IDs will be generated over time. The device information file as a fragmented file will occupy more storage space and will affect the speed of pushing broadcast messages. After each integration cycle, the device IDs stored in each new device information file corresponding to the target APP generated in the integration cycle are integrated into one or a few device information files, and then the device IDs corresponding to the target APP The new device information file is deleted, which can reduce the number of fragmented files, and can ensure the speed of pushing broadcast messages while saving storage resources.

In the following, in conjunction with specific examples, the APP broadcast message push method provided in the embodiments of the present application will be further described in detail. As shown in FIG. 5, the method may include the following steps:

Step 501: Look up the device ID associated with the target APP from the database. In the embodiment of the present application, the association relationship between different APPs and device IDs is stored in the database, and the mobile phone device corresponding to the device ID that has an association relationship with an APP is installed with the APP. According to the association relationship of the design target APP in the database, the device ID corresponding to each association relationship found is determined as the device ID associated with the target APP. For example, the database stores the association relationship between 10 different APPs and device IDs. Now take APP1 as the target APP, search for the association relationship involving APP1 from the database, and query a total of 20 million device IDs and APP1 association relationships, and then determine 20 million corresponding to APP1 based on these 20 million association relationships The device ID.

Step 502: Create a device information file corresponding to the target APP according to the number of device IDs queried. In the embodiment of the present application, after the device ID associated with the target APP is queried, the number of device information files to be created is determined according to the number of device IDs queried, and then a corresponding number of device information files are created. Specifically, the number of device information files to be created can be determined according to the following formula;

Among them, M represents the number of required device information files; x represents the number of device IDs found in the database and associated with the target APP; X represents a preset number threshold; m represents a broadcast message push device The maximum number of message push threads that can be run; k represents a constant determined according to the maximum number of device IDs that can be stored in a device information file;

For example, in the above formula, X has a value of 1 million and k has a value of 98,000. Since the number of device IDs found to be associated with APP1 x is equal to 20 million,

That is, create 205 single device information files that can store up to 100,000 device IDs as the device information files corresponding to APP1.

Step 503: Store the queried device IDs in the created device information files. In the embodiment of this application, after the device information file corresponding to the target APP is created, each device ID associated with the target APP is stored in each device information file corresponding to the target APP, and then the device ID is stored All equipment information files are stored uniformly. Specifically, the priority distribution information can be calculated according to the priority analysis and statistics of each device ID associated with the target APP, and then a corresponding priority file can be set for each created device information file according to the priority distribution information Then, according to the priority of each device ID and the priority file proportion of each device information file, each device ID is stored in each device information file, so that the device ID of each device information file has a different priority. Occupy the proportion of priority files corresponding to the device information file. For example, 20 million device IDs associated with APP1 are stored in 205 device information files corresponding to APP1.

Step 504: Periodically store the newly-added device ID in the database and associated with the target APP into the newly created device information file. In the embodiment of the present application, after the device ID associated with the target APP is stored in the device information file corresponding to the target APP for the first time, after each update cycle, the database is searched for the new and added target APP in the database. The associated new device ID, and the found new device ID is stored in one or more newly created new device information files, and then the new device information file storing the new device ID will be the same as that created before The device information files corresponding to the target APP are stored together. In addition, every time an integration period that is larger than the update cycle time span passes, the newly added device ID stored in the newly added device information file created during the integration period is integrated into one or more device information files, and then the integrated The obtained device information file is stored, and the newly integrated device information file is deleted. For example, at 1:00 am every day, find the device ID associated with APP1 that was newly added to the database the day before from the database, and store the found device ID in a newly created new device information file, and then the new device ID The additional device information file is stored together with each device information file corresponding to APP1 obtained previously. In addition, after every one week, all new device information files corresponding to APP1 created in the previous week are integrated, and the device ID stored in each new device information file is integrated into a few device information files , Delete each newly-added device information file after integration, and store the device information file obtained after integration.

Step 505: Receive a broadcast message push instruction for the target APP. In the embodiment of the present application, the user's broadcast message push instruction for the target APP is received, that is, the user needs to push the broadcast message to the user through the target APP installed on the mobile phone.

Step 506: Create a corresponding number of message push threads according to the number of device information files corresponding to the target APP. In the embodiment of the present application, after receiving the broadcast message push instruction for the target APP, a corresponding number of message push threads are created according to the number of stored device information files corresponding to the target APP. For example, after receiving a broadcast message push instruction for APP1, it is determined that there are 210 device information files corresponding to APP1, and 210 message push threads are created.

Step 507: Run each message pushing thread at the same time to push the broadcast message to the mobile device according to the device ID stored in each device information file. In the embodiment of the present application, after multiple message push threads are created, the created message push threads are run at the same time, so that the message push threads are parallel. After each message push thread starts running, it reads the device ID in turn from its corresponding device information file, and pushes the broadcast message to the corresponding mobile device according to the read device ID, and the specific content of the broadcast message can be Obtain from the received broadcast message push instruction. For example, the created 210 message push threads correspond to 210 device information files corresponding to APP1, each message push thread corresponds to one device information file, and different message push threads correspond to different device information files. Each message push thread sequentially reads the device ID from the corresponding device information file, and pushes the broadcast message to the corresponding mobile device according to the read device ID.

As shown in FIG. 6, an embodiment of the present application provides an APP broadcast message pushing device, including: a storage module 601, a receiving module 602, an obtaining module 603, and a pushing module 604;

The storage module 601 is used to search for a device ID associated with the target APP from a database for any target APP, and store each device ID found in at least one device information file corresponding to the target APP; receiving module 602, configured to receive a broadcast message push instruction for the target APP; the acquiring module 603, configured to acquire at least one device information file generated by the storage module 601 and corresponding to the target APP according to the broadcast message push instruction received by the receiving module 602 The push module 604 is used to push the broadcast message to the mobile phone device corresponding to the device ID according to the device ID stored in each device information file acquired by the acquisition module 603. In the embodiment of the present application, the storage module 601 can be used to execute

steps

101, 201 to 203, steps 301 to 303, and steps 501 to 503 in the above method embodiment, and the receiving module 602 can be used to execute the steps in the above method embodiment 102 and step 505, the acquisition module 603 can be used to execute step 103 in the above method embodiment, and the push module 604 can be used to execute step 104 and steps 506 to 507 in the above method embodiment.

It should be noted that the information exchange and execution process among the various modules included in the device embodiment are based on the same application concept as the above method embodiment, and the specific content can be referred to the description in the above method embodiment. No longer. In addition, this device embodiment may also include other modules for executing each step in the foregoing method embodiment.

An embodiment of the present application also provides a computer device, including a memory and a processor, and computer-readable instructions are stored in the memory. When the processor executes the computer-readable instructions stored in the memory, the above-mentioned various embodiments can be implemented. The APP broadcast message push method. The embodiments of the present application also provide a non-volatile readable storage medium with computer readable instructions stored on the computer readable storage medium, and when the stored computer storage is executed, the above-mentioned various embodiments can be implemented. APP broadcast message push method.

In summary, the APP broadcast message push method, device, computer equipment, and computer-readable storage medium provided by the various embodiments of the present application pre-store each device ID associated with the target APP stored in the database to one or more In the device information file corresponding to the target APP, after receiving the broadcast message push instruction for the target APP, obtain each device information file corresponding to the target APP, and then according to the device ID stored in each obtained device information file Push broadcast messages to corresponding mobile devices. It can be seen that each device ID associated with the same APP is stored in one or more device information files in advance, and after receiving the broadcast message push instruction for the APP, it is directly based on the device information files corresponding to the APP. The device ID stored in the device pushes the broadcast message to the corresponding mobile device. There is no need to temporarily find the device ID associated with the APP from the database after receiving the broadcast message push instruction, thereby improving the efficiency of pushing broadcast messages to users through the APP .

It should be noted that in this article, the terms "including", "including" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, device, article or method including a series of elements not only includes those elements, It also includes other elements that are not explicitly listed, or elements inherent to the process, device, article, or method. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, device, article or method that includes the element. The serial numbers of the foregoing embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments. Through the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM) as described above. , Magnetic disk, optical disk), including several instructions to make a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) execute the method described in each embodiment of the present application. The above are only preferred embodiments of this application, and do not limit the scope of this application. Any equivalent structure or equivalent process transformation made using the content of the description and drawings of this application, or directly or indirectly used in other related technical fields , The same reason is included in the scope of patent protection of this application.

Claims

A method for pushing APP broadcast messages. For any target APP, search for the device ID associated with the target APP from a database, and store each of the found device IDs in at least one corresponding to the target APP. A device information file also includes:

Receiving a broadcast message push instruction for the target APP;

Obtaining at least one device information file corresponding to the target APP according to the broadcast message push instruction;

Pushing a broadcast message to the mobile phone device corresponding to the device ID according to the device ID stored in each of the device information files obtained includes: creating a corresponding message for each device information file obtained The message push thread; at the same time each of the message push threads created to run, so that each message push thread according to the corresponding device ID stored in the device information file, to the corresponding The mobile phone device pushes the broadcast message.
The method according to claim 1, after the device ID associated with the target APP is searched from the database, and each of the device IDs found is stored in at least one corresponding to the target APP Before a device information file, it further includes:

According to the number of device IDs associated with the target APP found in the database, the number of required device information files is determined by the following formula;

Wherein, the M characterizes the number of the required device information files; the x characterizes the number of the device IDs that are found in the database and is associated with the target APP; the X characterizes the number of device IDs associated with the target APP; The set number threshold; the m represents the maximum number of message push threads that can be run by a broadcast message push device; the k represents the maximum number of device IDs that can be stored according to one device information file A constant determined by the number;

According to the determined number of the required device information files, a corresponding number of the device information files are created.
The method according to claim 1, wherein storing each of the found device IDs in at least one device information file corresponding to the target APP comprises:

Perform statistics on the priority of each of the found device IDs, and determine the priority distribution information of each of the found device IDs;

Respectively setting a corresponding priority file proportion for each device information file according to the priority distribution information;

According to the priority of each device ID found and the proportion of the priority file corresponding to each device information file, each of the device IDs found is stored in each device information file, so that The proportions of the device IDs of different priorities in each of the device information files conform to the proportions of the corresponding priority files.
The method according to claim 1, after storing each of the found device IDs in at least one device information file corresponding to the target APP, further comprising:

After a preset update period, search the database for the newly added device ID associated with the target APP, where the newly added device ID is added to the database during the update period Device ID in;

Creating at least one newly added device information file corresponding to the target APP;

Store each of the newly-added device IDs found in the at least one newly-added device information file.
The method according to claim 4, before the storing each of the newly-added device IDs found in the at least one newly-added device information file, further comprising:

The priority is configured for each of the newly added device IDs found.
The method of claim 4, further comprising:

After each pre-set integration period, query each of the newly added device information files created in the integration period;

Integrating the newly-added device ID stored in each of the newly-inquired newly-added device information files into at least one device information file, and deleting each of the newly-inquired newly-added device information files.
An APP broadcast message pushing device, including: a storage module, a receiving module, an acquisition module, and a pushing module;

The storage module is configured to search for a device ID associated with the target APP from a database for any target APP, and store each of the device IDs found in at least one corresponding to the target APP In the equipment information file;

The receiving module is configured to receive a broadcast message push instruction for the target APP;

The obtaining module is configured to obtain at least one of the device information files generated by the storage module and corresponding to the target APP according to the broadcast message push instruction received by the receiving module;

The pushing module is configured to push a broadcast message to the mobile phone device corresponding to the device ID according to the device ID stored in each device information file acquired by the acquisition module;

The push module is specifically configured to create a corresponding message push thread for each acquired device information file; at the same time, run each of the created message push threads to make each message push thread Push a broadcast message to the corresponding mobile phone device according to the device ID stored in the corresponding device information file.
The apparatus according to claim 7, wherein the storage module is further configured to determine the required device information according to the number of the device IDs associated with the target APP found in the database by the following formula The number of files;

Wherein, the M characterizes the number of the required device information files; the x characterizes the number of the device IDs that are found in the database and is associated with the target APP; the X characterizes the number of device IDs associated with the target APP; The set number threshold; the m represents the maximum number of message push threads that can be run by a broadcast message push device; the k represents the maximum number of device IDs that can be stored according to one device information file A constant determined by the number;
According to the determined number of the required device information files, a corresponding number of the device information files are created.
The apparatus according to claim 7, wherein the storage module is specifically configured to collect statistics on the priority of each of the device IDs found, and determine the priority distribution information of each of the device IDs found; Priority distribution information sets a corresponding priority file ratio for each device information file; according to the priority of each device ID found and the priority file corresponding to each device information file The proportion of each device ID found is stored in each device information file, so that the proportion of the device ID with different priorities in each device information file conforms to the corresponding priority File ratio.
The apparatus according to claim 7, wherein the storage module is further configured to search the database for the newly-added device ID associated with the target APP every time a preset update period has passed, wherein the The newly added device ID is the device ID added to the database during the update period; at least one newly added device information file corresponding to the target APP is created; each of the newly added device IDs found Stored in the at least one newly added device information file.
The apparatus according to claim 10, wherein the storage module is further configured to configure a priority for each newly-added device ID found.
The device according to claim 10, the storage module is further configured to query each of the newly-added equipment information files created during the integration period after a preset integration period; The newly-added device ID stored in the newly-added device information file is integrated into at least one device information file, and each of the newly-inquired device information files is deleted.
A computer device includes a memory and a processor, the memory stores computer-readable instructions, and the processor implements an APP broadcast message push method when the computer-readable instructions are executed, and searches for any target APP from a database The device ID associated with the target APP, and storing each of the found device IDs in at least one device information file corresponding to the target APP, further includes: receiving a broadcast message for the target APP Push instruction; according to the broadcast message push instruction, obtain at least one of the device information files corresponding to the target APP; according to the device ID stored in each of the obtained device information files, Pushing the broadcast message by the mobile phone device corresponding to the device ID includes: creating a corresponding message push thread for each acquired device information file; at the same time, running each of the created message push threads so that each One of the message pushing threads pushes the broadcast message to the corresponding mobile phone device according to the device ID stored in the corresponding device information file.
The computer device according to claim 13, when the processor executes the computer-readable instruction to implement the method, after the device ID associated with the target APP is searched in the database, and after the Before each of the found device IDs is stored in at least one device information file corresponding to the target APP, the method further includes: according to the device IDs found in the database and associated with the target APP The number of equipment information files required is determined by the following formula;

Wherein, the M characterizes the number of the required device information files; the x characterizes the number of the device IDs that are found in the database and is associated with the target APP; the X characterizes the number of device IDs associated with the target APP; The set number threshold; the m represents the maximum number of message push threads that can be run by a broadcast message push device; the k represents the maximum number of device IDs that can be stored according to one device information file A constant determined by the number;
According to the determined number of the required device information files, a corresponding number of the device information files are created.
The computer device according to claim 13, wherein when the processor executes the computer-readable instruction, storing each of the device IDs found in at least one device information file corresponding to the target APP is implemented , Including: performing statistics on the priority of each of the device IDs found, and determining the priority distribution information of each of the device IDs found; setting the device information file separately according to the priority distribution information The proportion of corresponding priority files; according to the priority of each device ID found and the proportion of the priority file corresponding to each device information file, store each of the device IDs found in In each of the device information files, the proportion of the device IDs with different priorities in each of the device information files is made to conform to the proportion of the corresponding priority files.
The computer device according to claim 13, wherein when the processor executes the computer-readable instruction, the device ID is stored in at least one device information file corresponding to the target APP. After the middle, it further includes: searching the database for the newly-added device ID associated with the target APP every time a preset update period has elapsed, wherein the newly-added device ID is within the update period Device ID added to the database; creating at least one new device information file corresponding to the target APP; storing each of the new device IDs found in the at least one new device information file in.
A non-volatile readable storage medium, on which computer readable instructions are stored, when the computer readable instructions are executed by a processor, an APP broadcast message push method is realized, and for any target APP, search and all data from the database The device ID associated with the target APP, and storing each of the found device IDs in at least one device information file corresponding to the target APP, further includes: receiving a broadcast message push instruction for the target APP According to the broadcast message push instruction, obtain at least one of the device information files corresponding to the target APP; according to the device ID stored in each of the obtained device information files, to the device The mobile phone device corresponding to the ID pushes the broadcast message, including: creating a corresponding message push thread for each acquired device information file; at the same time, running each of the created message push threads to make each The message pushing thread pushes the broadcast message to the corresponding mobile phone device according to the device ID stored in the corresponding device information file.
The storage medium according to claim 17, when the computer-readable instructions are executed by a processor to implement the method, after the device ID associated with the target APP is searched in the database, and after searching Before each of the obtained device IDs is stored in at least one device information file corresponding to the target APP, it further includes: according to the device ID found in the database and associated with the target APP Number, determine the number of equipment information files required by the following formula;

Wherein, the M characterizes the number of the required device information files; the x characterizes the number of the device IDs that are found in the database and is associated with the target APP; the X characterizes the number of device IDs associated with the target APP; The set number threshold; the m represents the maximum number of message push threads that can be run by a broadcast message push device; the k represents the maximum number of device IDs that can be stored according to one device information file A constant determined by the number;
According to the determined number of the required device information files, a corresponding number of the device information files are created.
The storage medium according to claim 17, wherein the processor executes the computer-readable instruction to store each of the device IDs found in at least one device information file corresponding to the target APP , Including: performing statistics on the priority of each of the device IDs found, and determining the priority distribution information of each of the device IDs found; setting the device information file separately according to the priority distribution information The proportion of corresponding priority files; according to the priority of each device ID found and the proportion of the priority file corresponding to each device information file, store each of the device IDs found in In each of the device information files, the proportion of the device IDs with different priorities in each of the device information files is made to conform to the proportion of the corresponding priority files.
The storage medium according to claim 17, when the processor executes the computer-readable instructions, the processor stores each of the device IDs found in at least one device information file corresponding to the target APP. After the middle, it further includes: searching the database for the newly-added device ID associated with the target APP every time a preset update period has elapsed, wherein the newly-added device ID is within the update period Device ID added to the database; creating at least one new device information file corresponding to the target APP; storing each of the new device IDs found in the at least one new device information file in.