A SEM push method, system and device

Abstract

The present invention provides a SEM push method, system and device, the method comprising the following steps: obtaining user device information, storing the user device information in a database according to different user device platforms; creating a push task according to the user device information; calling a first platform interface corresponding to the user device to execute the push task; calling a second platform interface corresponding to the user device to obtain push result information of the push task. The SEM push method of the present invention can greatly increase the proportion of push messages reaching devices, achieving push marketing effects.

Description

Technical Field

[0001] The present invention belongs to the technical field of data push service, and in particular relates to a SEM push method, system and device. Background Art

[0002] In the Internet wave, mobile Internet has emerged as a new force, and a large number of mobile client software have emerged in front of users like a hundred flowers blooming. The content of the message seen by users is particularly important. Considering the cost, SEM (Search Engine Marketing) push service technology can solve this problem. Push technology refers to establishing a long link between the client and the server, and the client can receive messages sent by the server at irregular intervals. At present, the most widely used push technologies are U-PUSH and APNS, among which:

[0003] U-PUSH is a precise message push tool created by Umeng+ for App developers. It supports multi-platform distribution, seamless message withdrawal, and precise group push. It covers channels of multiple manufacturers including Huawei, Xiaomi, and Meizu, and improves user activity and stickiness.

[0004] APNS (Apple Push Notification service) is a push notification service launched by Apple. Apple Push Notification Service transmits and routes notifications from a given provider to a given device. Notifications are composed of two main parts of data: device token and payload short message. Device token is similar to a phone number, it contains information that enables APNS to locate the device on which the client application is installed.

[0005] Push can solve the problem of the client receiving messages from the server. When pushing messages to various types of terminals, third-party push services are usually used, such as Umeng, Jiguang, and Getui. This method requires the client to provide a unique identifier for the client device, and then the client, the third party (middleman), pushes the messages in batches to different types of terminal devices. However, using third-party push is prone to situations such as the push process being intercepted and the system being offline. In addition, third-party push is only responsible for executing the push operation itself, and does not provide feedback on the push arrival results, making it impossible to analyze and improve the push.

[0006] Therefore, how to solve the above-mentioned problem of low arrival rate of message push to user terminal devices and inability to count push results is a technical problem that urgently needs to be solved in this field. Summary of the invention

[0007] In view of the above problems, the present invention provides a SEM pushing method, system and device.

[0008] A SEM push method comprises the following steps:

[0009] Obtain user device information, and store the user device information in a database according to different user device platforms;

[0010] Create push tasks based on user device information;

[0011] Calling a first platform interface corresponding to the user device to execute the push task;

[0012] A second platform interface corresponding to the user device is called to obtain push result information of the push task.

[0013] Furthermore, the method further comprises:

[0014] The user device information is updated according to the application login information on the user device.

[0015] Furthermore, it also includes:

[0016] According to the push result information, statistics are collected on the push data arrival volume, opening volume and SEM conversion volume.

[0017] Further, the arrival result of the push task is obtained by asynchronously calling back the second platform interface, and the number of push messages arriving at the user device is counted as the arrival amount;

[0018] The client uploads the opening records of the push task to the server to realize the opening quantity statistics;

[0019] Through big data analysis, the operations of designated users related to the push task are obtained, and the operations of designated users are used as the conversion results of the push task to achieve SEM conversion volume statistics.

[0020] Further, creating a push task according to the user device information includes:

[0021] Dynamically create push tasks based on user device information and template information.

[0022] Further, the template information includes a wildcard, and the dynamically creating a push task according to the user device information and the template information includes:

[0023] Obtain user information based on user device information;

[0024] Generate push messages for users by replacing wildcards based on user information;

[0025] Generate push tasks based on user device information and push messages.

[0026] Furthermore, it also includes:

[0027] After creating the push task, store it in the redis queue;

[0028] When executing the push task, multiple threads are used to extract tasks from the redis queue in parallel and execute them.

[0029] Furthermore, when executing the push task, a push request is sent through the GuzzleHttp pool.

[0030] The present invention also provides a SEM pushing system, the SEM pushing system comprising:

[0031] A user equipment information acquisition unit, used to acquire user equipment information and store the user equipment information in a database according to different user equipment platforms;

[0032] A push task creation unit, used to create a push task according to user device information;

[0033] A push task execution unit, configured to call a first platform interface corresponding to the user device to execute the push task;

[0034] The push result information acquisition unit is used to call the second platform interface corresponding to the user device to acquire the push result information of the push task.

[0035] The present invention also provides a SEM pushing device, the device comprising at least one processor and at least one memory;

[0036] The memory stores a computer program for executing the SEM pushing method, and the processor calls the computer program in the memory to execute the SEM pushing method.

[0037] The present invention does not have the role of a middleman, and sends the push data to the user device, providing a one-stop push service to improve operational work efficiency. The SEM push method described in the present invention directly uses the platform interface corresponding to the user device to push the data to be pushed to the user device, that is, directly uses the manufacturer channel to push. The various types of user devices have their own manufacturer channels. The manufacturer channels have a good solution for push interception when the user devices of their own factories are offline, which can greatly increase the proportion of push messages reaching the device and achieve push marketing effects. At the same time, the present invention also uses the platform interface to count the push result information of the data to be pushed, that is, uses the manufacturer channel to count the push result information, which helps to refine user analysis, facilitates understanding of its business scope, and improves push efficiency and user comfort.

[0038] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0040] Figure 1 is a flow chart of a SEM push method according to an embodiment of the present invention;

[0041] Figure 2 A flowchart of creating a task using a template according to an embodiment of the present invention;

[0042] Figure 3 A flowchart of executing a SEM push plan according to an embodiment of the present invention;

[0043] Figure 4 A schematic diagram of the structure of a SEM push system according to an embodiment of the present invention;

[0044] Figure 5 Schematic diagram of the structure of a SEM pushing device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0046] Please refer to Figure 1 This embodiment provides a SEM push method, including the following steps:

[0047] Step 1: Obtain user device information and store the user device information in a database according to different user device platforms;

[0048] Step 2: Create a push task based on the user's device information;

[0049] Step 3: calling the first platform interface corresponding to the user device to execute the push task;

[0050] Step 4: calling the second platform interface corresponding to the user device to collect statistics on push result information of the push task.

[0051] The user device described in this embodiment refers to a mobile terminal that can install an application client program, i.e., an APP, such as a mobile phone, a tablet computer, etc. The various types of user devices described have their own manufacturer channels. The manufacturer channels have a good solution for offline push interception of their own user devices, which can greatly increase the proportion of messages reaching devices and effectively improve the message arrival rate. At the same time, the embodiment of the present invention also uses the platform interface to count the push result information of the push task, that is, using the manufacturer channel to count the push result information, which helps to refine the users, facilitate understanding of their business scope, and improve push efficiency and user comfort. The following is a detailed description of each step of the above method.

[0052] In step 1, user devices may include mobile terminals of various manufacturers, such as mobile phones, tablet computers, etc. A user device information is stored as a json record, so that it is convenient to store and expand uniformly for different platform types and different user device identifiers. MongoDB is used as the database for storing user device json information. MongoDB is a database based on distributed file storage, which has fast query and is convenient for parsing according to business scenarios, which helps to improve push efficiency.

[0053] Different manufacturers (platforms) have different platform device identifiers for user devices. In the embodiment of the present invention, user devices of multiple different platforms are further divided into two categories, namely Android platform and iOS platform, so that task push planning and processing can be performed according to needs and platform differences. The platform category identifier is also stored in the user device information. Android platform devices are identified by "imei". Under this category, there are also different setting products of various manufacturers. User device information, such as device manufacturer and unique ID, is recorded separately according to the differences between manufacturer platforms to form the above json record. The iOS platform is identified by "idfa".

[0054] In order to ensure the real-time nature of user device information, the embodiments of the present invention also update user device information based on the client usage information on the user device. After the user installs the client on the device, the client can obtain relevant information about the user device, and feed back the device information of the client to the server of the push service, thereby recording the user device information. The client refers to the application software installed on the user device that performs specific business functions. However, the user may change the device, such as re-downloading and logging into the client after changing the mobile phone. At this time, the device information of the specified registered user is obtained based on the client information, and the new device information is sent to the server, and the server adds or updates the device information based on the customer information. In the embodiments of the present invention, the user device information is dynamically obtained through the client usage information, which improves the accuracy of the user device information, thereby improving the arrival rate of information transmission.

[0055] In step 2, a push task is created according to the user device information, including: dynamically creating a push task according to the user device information and template information. The template information includes wildcards. The process of using the template to create a task is as follows: Figure 2 As shown:

[0056] Step 2-1: Obtain user information based on user device information;

[0057] Step 2-2: Replace the wildcard character according to the user information to generate a push message for the user;

[0058] Step 2-3: Generate a push task based on the user device information and the push message.

[0059] Specifically, the template information includes template name, title, content, etc. Multiple template information can be stored in the server and can be continuously updated according to operation data, period, season, etc., so as to promote the content of the pushed data to improve sales targets. When creating a push task, select the corresponding specified template information for the specified user according to business needs, that is, what content is pushed to which user devices.

[0060] Among them, this embodiment adds wildcards to the text of the template information, and replaces the wildcard content according to the user's preference behavior, so as to achieve a thousand-faced effect. For example: "The {brand} {car series} you are interested in {region} is now reduced in price!!!".

[0061] The push task adopts a unified format. Because the push architecture is divided into two parts: production and consumption, a unified template is used in the production step, and in the consumption process, each push channel has a unified parsing template, which can achieve a unified processing effect when push channels are developed by different people.

[0062] Taking the above template message as an example, obtaining user information includes obtaining user location information, user browsing information, etc. The user location information is obtained through the user device information, such as obtaining that the user device is located in Beijing. The user browsing information generates user preference data based on the browsing history of the user client counted by the server. For example, if the user recently prefers to browse BMW series vehicles, the wildcard in the template information is replaced to generate the final push message "The BMW 5 Series you are interested in in Beijing is now reduced in price!!!" In an embodiment of the present invention, using template wildcards and user information, push messages that are consistent with user information can be sent to a variety of users, thereby improving the user stickiness of the client. According to the requirements, all pushed messages are unicast. Unicast is a communication between a single sender and a receiver through the network. Unicast can customize specific copywriting and generate customized copywriting based on wildcards and user preferences. Achieve a thousand-faced effect.

[0063] The generated push tasks are stored in the redis queue, which supports adding, deleting or querying the push tasks. Specifically, redis: Remote Dictionary Server, that is, remote dictionary service, is an open source log-type, Key-Value database written in ANSI C language, supporting the network, memory-based and persistent, and provides APIs in multiple languages. The present invention uniformly generates push tasks for device users of different platform manufacturers. For example, push tasks of different platforms are encapsulated into json data in a unified format and stored in the redis queue so that multiple consumer threads can process tasks in the queue in parallel.

[0064] When a push task is generated, the configuration file of the push task is parsed, and the push task is stored according to the parsing result. The configuration file of the push task is a push parameter configuration, which records the key parameters such as the parameters required for the push, storage location, and queue information. Putting the configuration in one file helps reduce maintenance costs.

[0065] In step 3, multiple threads are used to extract tasks from the redis queue in parallel and execute message push. A consumer thread refers to a thread that obtains and processes tasks from a specified location. After a task is obtained by one of the consumers, other consumers no longer need to process the task, and the task is removed from the queue. Thus, multiple consumers can concurrently collaborate to process the overall push task, thereby improving the efficiency of message sending. Specifically, when the system has more than one CPU, the operation of the thread may be non-concurrent. When one CPU executes a thread, another CPU can execute another thread. The two threads do not preempt each other's CPU resources and can be performed at the same time. This method is called parallel. The use of redis queues can better support concurrent processing. Concurrency in the embodiment of the present invention refers to that in the operating system, concurrency refers to the fact that several programs in a time period are between started and completed, and these programs are all running on the same processor, but only one program is running on the processor at any time point. In addition, the generation of tasks and the processing of tasks can also be performed synchronously. The consumer thread parses the push task, and reassembles the data structure required by the push platform according to the different target manufacturer platforms of the task push, that is, calls the parameters required by the first platform interface of the corresponding platform, and then calls the first platform interface through the manufacturer channel. The first platform interface is an interface provided by the manufacturer to execute push messages to the user device, and the interface is provided in the form of a web service. In the embodiment of the present invention, in order to make full use of system resources and further improve the push efficiency. Task push uses GuzzleHttp technology to implement parallel processing of push requests. When each channel sends a request, it will use GuzzleHttp's request pool to push. Because this technology is based on user-mode operations, it implements coroutine technology and fairly uses CPU resources during the push process, so it can play a better concurrency effect. Guzzle is a PHP HTTP client used to send requests and integrated into the WEB service. Guzzle has a simple interface, can send synchronous or asynchronous requests using the same interface, uses the PSR-7 interface to request, respond, and divert, and allows the use of other compatible PSR-7 libraries to be developed with Guzzle; abstracts the underlying HTTP transmission, allows the environment and other codes to be changed; the middleware system allows the creation of client behaviors and other advantages. Therefore, using GuzzleHttp technology to implement parallel processing of push requests can achieve higher push efficiency and facilitate the start of multiple push service processes.

[0066] In step 4, the push result information is obtained through the second platform interface. The push result information mainly includes whether the push task is successfully executed, that is, whether the push message reaches the user device. The second platform interface is another web service interface provided by the manufacturer platform to obtain the execution result of the first platform interface. In the embodiment of the present invention, the push result is obtained by asynchronously calling back the second platform interface. That is, the first platform interface call and the second platform interface call are executed asynchronously to ensure the efficiency of the push execution process.

[0067] In an embodiment of the present invention, the arrival volume, opening volume and SEM conversion volume of the push data are also counted according to the push result information. Among them, the arrival volume refers to the number of push messages that reach the user's device after the push task is successfully executed, and the push task arrival result is obtained by asynchronously calling back the second platform interface; the opening volume refers to the number of users who open the corresponding client after receiving the push information. When the customer clicks the push message to open the client, the opening record of the push task is uploaded to the server through the client to achieve the opening volume statistics. The SEM conversion volume is: tracking the user's operation on the client, obtaining the operation of the specified user related to the push task through big data analysis, as the conversion result of the push task, and realizing the SEM conversion volume statistics by counting the conversion results of the push task. Exemplarily, the specified operation is that the user leaves a phone number, purchases the corresponding product, etc. By counting the relevant results of the push task, the effect of the push can be known, and the push plan can be adjusted according to the push effect to provide a basis for business strategy.

[0068] The client provider generates task information as needed. Task information is a general task plan for pushing specified messages to users within a specified range. For example, sending holiday greeting messages to all users, or pushing new car launch messages to Android platform users. The following is an exemplary description of the process of executing task information according to the above method. In the implementation of the present invention, pushing messages to the Android platform is used as an example for explanation.

[0069] like Figure 3As shown, task information is obtained, and task information includes two categories: precise push and full push, such as push to all users and push to Android platform. In both cases, task push of Android platform needs to be executed. Specifically, user device information identified as "IMEI" is obtained from the database, and user device information is stored as JSON in the database. The ID, platform, etc. of user device information are parsed to obtain the ID, platform, etc. of user device information, and the token required for push (token, an object representing the right to perform certain operations) is obtained. The token required for push of different manufacturer platforms is different, and the token of the corresponding manufacturer is obtained respectively. Further, the storage configuration of device information is saved in the configuration file, and the configuration file is uploaded to the designated server. When obtaining user device information, the device information of the specified type is obtained from the designated database according to the configuration file. For the user information that is successfully parsed and the platform access token that is successfully obtained, the basic data is assembled, that is, a push task for the user is generated. In the embodiment of the present invention, a personalized push task for an individual user is generated according to the wildcard configuration in the push template. Then the generated push task is stored in the redis queue for consumption execution. The user devices of each manufacturer of the platform push messages. A push task is generated according to the push plan.

[0070] In an embodiment of the present invention, a cancellation mark is set for the task information so that in the process of generating tasks and executing queue tasks, the task can be terminated at any time according to the cancellation mark, avoiding the execution of unreasonable task messages and bringing about a wide range of adverse effects. Specifically, before storing after generating and pushing tasks, it is first determined whether the task information is cancelled. If it has been cancelled, the generated task is terminated. If it has not been cancelled, the generated task is placed in the redis queue. The task cancellation mark can be exemplarily a task cancellation variable mark corresponding to the specified redis queue, that is, a task data cancellation mark key corresponding to the redis queue key. The task cancellation mark of the redis queue can be updated after the user formulates the task information or in the process of executing task generation and task push. During the task generation process, the cancellation mark of the specified queue recorded in the update program is obtained in real time, that is, the redis task data cancellation mark. When storing tasks, it is determined whether to store the task according to the mark. When executing tasks, multiple threads extract tasks from the redis queue in parallel. Exemplarily, the json data of the stored tasks is obtained. If the task data fails to be obtained, the task execution process is terminated. When the task is extracted, there is no data in the queue, the extraction task fails, and the execution is terminated. When the task is successfully obtained, it is necessary to determine whether the task is cancelled. If the task cancellation flag is true, the push task will not be executed and will end directly. If the cancellation flag is false, that is, the task is not cancelled, the task will be executed.

[0071] When executing a task, the uniformly encapsulated task json data is parsed, reassembled into the data structure required for push corresponding to the user device platform, and then the corresponding manufacturer channel platform interface is called to execute the push. Before executing the push task, the platform interface checks whether the assembled data is abnormal, whether it meets the specifications for calling the platform interface, etc. If the data is abnormal, it is stored in the log module (model). If the data is normal, the platform interface call is executed through the GuzzleHttp pool. GuzzleHttp abstracts the underlying HTTP transmission, does not rely heavily on the stream or socket of cURL and PHP, and does not block the event loop. cURL is a tool that uses URL syntax to perform communication in a command manner, which supports file transfer of HTTP protocol. The embodiment of the present invention implements concurrent HTTP request sending through a cURL client (curlClient) based on GuzzleHttp, and calls the first platform interface to push the task. After the platform interface is called, the HTTP server returns the interface call result, which is the result of whether the first platform interface is successfully executed, and the result is stored in the log module. After executing a push task, the consumer thread continues to obtain new tasks from the task queue to execute. The result of whether the push has arrived is obtained asynchronously through the second platform interface, which is not shown in the figure.

[0072] This embodiment also discloses a SEM push system for implementing the above-mentioned SEM push method, such as Figure 4 As shown, the SEM push system includes a user device information acquisition unit, a push task creation unit, a push task execution unit and a push result information acquisition unit.

[0073] The user equipment information acquisition unit acquires the user equipment information and stores the user equipment information in a database according to different user equipment platforms.

[0074] The push task creation unit creates a push task according to the user device information, and specifically, dynamically creates a push task according to the user device information and the template information.

[0075] The template information includes a wildcard, and the dynamically creating a push task according to the user device information and the template information includes:

[0076] Obtain user information based on user device information;

[0077] Generate push messages for users by replacing wildcards based on user information;

[0078] Generate push tasks based on user device information and push messages.

[0079] After the push task is created, the push task is stored in the redis queue; when the push task is executed, multiple threads are used to extract the task from the redis queue in parallel and execute it.

[0080] A push task execution unit, calling a first platform interface corresponding to the user device to execute the push task;

[0081] The push result information acquisition unit calls the second platform interface corresponding to the user device to acquire the push result information of the push task.

[0082] Among them, the arrival volume, opening volume and SEM conversion volume of the push data are counted according to the push result information. Specifically, the arrival result of the push task is obtained by asynchronously calling back the second platform interface, and the number of push messages reaching the user device is counted as the arrival volume; the push task opening record is uploaded to the server through the client application to realize the opening volume statistics; through big data analysis, the designated user operation related to the push task is obtained, and the designated user operation is used as the conversion result of the push task to realize the SEM conversion volume statistics.

[0083] The template information includes a wildcard, and the dynamic creation of a push task based on the user device information and the template information includes: obtaining user information based on the user device information; replacing the wildcard based on the user information to generate a push message for the user; and generating a push task based on the user device information and the push message.

[0084] The specific implementation of the SEM push system described in this embodiment can refer to the specific implementation process of the above method embodiment, which will not be repeated here.

[0085] This embodiment also discloses a SEM pushing device, such as Figure 5 As shown, the device includes at least one processor and at least one memory, Figure 5 In the example, a processor and a memory are used; a communication interface and a bus may also be included. The processor, the communication interface, and the memory may communicate with each other through the bus. The communication interface may be used for information transmission. The processor may call the logic instructions in the memory to execute the SEM push method described in the above embodiment.

[0086] In addition, the logic instructions in the above-mentioned memory can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product.

[0087] The memory, as a computer-readable storage medium, can be used to store software programs and computer executable programs, such as program instructions / modules corresponding to the method in the embodiment of the present invention. The processor executes functional applications and data processing by running the software programs, instructions and modules stored in the memory, that is, implementing the method for SEM push in the above embodiment.

[0088] The memory may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required for at least one function; the data storage area may store data created according to the use of the terminal device, etc. In addition, the memory may include a high-speed random access memory and may also include a non-volatile memory.

[0089] The SEM push method, system and device of the embodiment of the present invention improve the success rate of push messages by directly calling the interface of the device platform, and obtain the results of push feedback, perform statistics, and provide a basis for business decision-making. Although the present invention is described in detail with reference to the aforementioned embodiments, ordinary technicians in this field should understand that it is still possible to modify the technical solutions recorded in the aforementioned embodiments, or to replace some of the technical features therein by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A SEM push method, characterized in that: The following steps are involved: Obtain user device information, and store the user device information in a database according to different user device platforms; wherein different user device platforms represent user devices of different manufacturer platforms; and create a push task according to the user device information; Calling a first platform interface corresponding to the user device to execute the push task; Calling a second platform interface corresponding to the user device, and acquiring push result information of the push task by asynchronously calling back the second platform interface; Among them, creating a push task based on user device information includes: Generate push tasks according to user device information corresponding to different user device platforms, and encapsulate the push tasks into a unified format and store them in the redis queue; the push architecture includes generation and consumption; Calling a first platform interface corresponding to the user device to execute the push task includes: Use multiple consumer threads to extract push tasks from the redis queue in parallel; After the consumer thread calls the first platform interface of the corresponding manufacturer platform of the user device with the required parameters, it calls the first platform interface through the manufacturer channel to execute the push task; Among them, the first platform interface is an interface provided by the manufacturer platform for executing push messages to user devices, and the interface is provided in the form of a web service.

2. The SEM pushing method according to claim 1, characterized in that: The SEM push method further includes: The user device information is updated according to the application login information on the user device.

3. The SEM pushing method according to claim 1, characterized in that: Also includes: According to the push result information, statistics are collected on the push data arrival volume, opening volume and SEM conversion volume.

4. The SEM pushing method according to claim 3, characterized in that: Obtain the arrival result of the push task by asynchronously calling back the second platform interface, and count the number of push messages arriving at the user device as the arrival amount; The client uploads the opening records of the push task to the server to realize the opening quantity statistics; Through big data analysis, the operations of designated users related to the push task are obtained, and the operations of designated users are used as the conversion results of the push task to achieve SEM conversion volume statistics.

5. The SEM pushing method according to claim 1, characterized in that: The creating a push task according to the user device information includes: Dynamically create push tasks based on user device information and template information.

6. The SEM pushing method according to claim 5, characterized in that: The template information includes a wildcard, and the dynamically creating a push task according to the user device information and the template information includes: Obtain user information based on user device information; Generate push messages for users by replacing wildcards based on user information; Generate push tasks based on user device information and push messages.

7. The SEM pushing method according to any one of claims 1 to 6, characterized in that: Also includes: After creating the push task, store it in the redis queue; When executing the push task, multiple threads are used to extract tasks from the redis queue in parallel and execute them.

8. The SEM pushing method according to claim 7, characterized in that: When executing the push task, a push request is sent through the GuzzleHttp pool.

9. A SEM push system, characterized in that: The SEM push system includes: A user equipment information acquisition unit, used to acquire user equipment information, and store the user equipment information in a database according to different user equipment platforms; wherein different user equipment platforms represent user equipment of different manufacturer platforms; A push task creation unit, used to create a push task according to user device information; A push task execution unit, configured to call a first platform interface corresponding to the user device to execute the push task; A push result information acquisition unit, configured to call a second platform interface corresponding to the user device and acquire push result information of the push task by asynchronously calling back the second platform interface; Among them, creating a push task based on user device information includes: Generate push tasks according to user device information corresponding to different user device platforms, and encapsulate the push tasks into a unified format and store them in the redis queue; the push architecture includes generation and consumption; Calling a first platform interface corresponding to the user device to execute the push task includes: Use multiple consumer threads to extract push tasks from the redis queue in parallel; After the consumer thread calls the first platform interface of the corresponding manufacturer platform of the user device with the required parameters, it calls the first platform interface through the manufacturer channel to execute the push task; Among them, the first platform interface is an interface provided by the manufacturer platform for executing push messages to user devices, and the interface is provided in the form of a web service.

10. A SEM pushing device, characterized in that: The apparatus comprises at least one processor and at least one memory; The memory stores a computer program for executing the method according to any one of claims 1 to 8, and the processor calls the computer program in the memory to execute the method according to any one of claims 1 to 8.

Images