CN115589432A

CN115589432A - Message push management method, device, medium and equipment

Info

Publication number: CN115589432A
Application number: CN202211294585.3A
Authority: CN
Inventors: 桑文锋; 曹犟; 刘耀洲; 付力力; 关海南
Original assignee: Sensors Data Network Technology Beijing Co Ltd
Current assignee: Sensors Data Network Technology Beijing Co Ltd
Priority date: 2022-10-21
Filing date: 2022-10-21
Publication date: 2023-01-10

Abstract

The embodiment of the application provides a message push management method, a message push management device, a message push management medium and message push management equipment, wherein the method comprises the following steps: obtaining a batch of messages to be sent, and analyzing and judging the batch of messages to be sent to obtain an analysis and judgment result; determining the sending authority of the batch of messages to be sent according to the analysis and judgment result; determining target messages to be sent with sending permission, and generating message touch tasks of the target messages to be sent according to attribute information contained in the target messages to be sent; storing the message touch task of each target message to be sent to the distributed storage of the flink distributed big data computing engine; and pushing the target message to be sent in the distributed storage to the corresponding client. By utilizing the embodiment of the application, the node for storing the message reach task is deployed in the flink distributed big data computing engine, so that mysql calling operation is carried out from the database once when the reach limit is not required to be judged every time, and the timeliness of message reach judgment is influenced.

Description

Message push management method, device, medium and equipment

Technical Field

The present application relates to the field of electronic communications technologies, and in particular, to a method, an apparatus, a medium, and a device for managing message pushing.

Background

In the field of big data marketing systems, people of a certain magnitude are usually selected through a series of rules, and then message reach is performed on the part of people. Such as short message reach, popup reach, weChat reach, push reach, or webhook reach. But as a big data marketing system, the user volume level reached each time can reach the level of tens of millions or even hundreds of millions, so that the accurate and quick sending of the big data level message is an important technical point of a push system.

The push system has an important link, namely the limitation is reached, for example, within 10 days, the number of messages pushed to a user is not more than N, and the excessive messages may cause harassment to the user. The limited dimensionality of a single user is multiple, for example, the limited dimensionality is more and more, the type level of a touch channel (short message, push, weChat and the like), the level of the touch channel (aurora push, chuanlan push and the like), the level of a touch channel account number (for example, an account number pushed by aurora), the level of a pushing strategy of a marketing canvas and the like are reached. And meanwhile, the limitation of combination types also occurs, such as the touch limit of combining a plurality of touch channels or the touch limit of combining a plurality of trigger channel account levels.

Therefore, the performance, accuracy, and scalability of reach constraints are very important for a reach system.

In the prior art, a message reach task is generally stored in a database, a computing layer uses a flink distributed big data computing engine, and when a single user is sent each time, the message reach task takes data within a fixed time range through the database, and then the judgment is carried out through the flink computing layer. The above scheme has several problems:

1. a database such as mysql/oracle has a larger performance bottleneck at high concurrency, and cannot support large concurrency during aggregation calculation;

flink is a big data computing engine, is deployed in different nodes with a database, and has mysql to call once when the touch limit is judged each time, so that the problem of short wooden barrel plates is obvious;

3. the database generally has an upper storage limit, but in a big data scene, the message reaching tasks of different dimensions of each user need to be recorded, and the database generally does not have the distributed expansion capability and has obvious storage and performance bottlenecks;

4. the dimensionality of the reach limit is gradually increased, and in the prior art, additional more development amount and expansibility deviation are needed for the newly increased dimensionality.

Disclosure of Invention

By utilizing the message push management method provided by the embodiment of the application, the node for storing the message reach task is deployed in the flink distributed big data computing engine, so that mysql is called from the database once without judging the reach limit every time, and the timeliness of message reach judgment is influenced.

An aspect of the present application provides a message pushing management method, which is used for a flink distributed big data computing engine, and includes:

obtaining a batch of messages to be sent, and analyzing and judging the batch of messages to be sent to obtain an analysis and judgment result;

determining the sending permission of the batch of messages to be sent according to the analysis and judgment result;

determining target messages to be sent with sending permission, and generating message touch tasks of the target messages to be sent according to attribute information contained in the target messages to be sent;

storing the message touch task of each target message to be sent to the distributed storage of the flink distributed big data computing engine;

and guiding the flink distributed big data computing engine to push the target message to be sent in the distributed storage to a corresponding client according to the description content of the message reach task.

In the message push management method according to the embodiment of the present application, the attribute information includes a trigger channel type level, a trigger channel account level, and a push policy level.

In the message push management method according to the embodiment of the present application, the generating a message reach task of each target message to be sent according to attribute information included in the target message to be sent includes:

according to the type level of the touch channel, the level of a trigger channel account number and the level of a push strategy, the touch channel type, the touch channel, the trigger channel account number and the push strategy which correspond to each limited dimension are obtained;

and generating a message reach task which corresponds to each target message to be sent and comprises a reach channel type, a reach channel account number and a push strategy.

In the message push management method according to the embodiment of the present application, after the target message to be sent is pushed to the push address corresponding to the target message to be sent according to the determined message sending manner, the method further includes:

acquiring a message sending state, and executing corresponding operation according to the message sending state;

if the message sending state is successful, generating a sending success event;

and if the message sending state is sending failure, generating a sending failure event, and deleting a message reach task corresponding to the sending failure from the distributed storage.

In the message push management method according to the embodiment of the present application, the method further includes:

and storing the message reach task to an external hdfs distributed storage.

In the message push management method according to the embodiment of the present application, the storing the message reach task of each target message to be sent to the distributed storage of the flink distributed big data computing engine includes:

serializing the message reach task by adopting a forward compatible mode of a serialization protocol of protobuf, so that the data structure of the message reach task is unified;

and storing the message reach task after the serialization processing to the distributed storage.

Correspondingly, another aspect of the embodiments of the present application further provides a message pushing management system, configured to be used in a flink distributed big data computing engine, where the message pushing management system includes:

and guiding the flink distributed big data computing engine to execute and push the target message to be sent in the distributed storage to the corresponding client according to the description content of the message reach task.

Accordingly, another aspect of the embodiments of the present application further provides a storage medium, where the storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to perform the message push management method described above.

Correspondingly, another aspect of the embodiment of the present application further provides a terminal device, including a processor and a memory, where the memory stores multiple instructions, and the processor loads the instructions to execute the message push management method described above.

The embodiment of the application provides a message push management method, a message push management device, a message push management medium and message push management equipment, wherein the method is used for a flink distributed big data computing engine and comprises the following steps: obtaining a batch of messages to be sent, and analyzing and judging the batch of messages to be sent to obtain an analysis and judgment result; determining the sending permission of the batch of messages to be sent according to the analysis and judgment result; determining target messages to be sent with sending permission, and generating message touch tasks of the target messages to be sent according to attribute information contained in the target messages to be sent; storing the message touch task of each target message to be sent to the distributed storage of the flink distributed big data computing engine; and guiding the flink distributed big data computing engine to execute and push the target message to be sent in the distributed storage to the corresponding client according to the description content of the message reach task. By utilizing the message push management method provided by the embodiment of the application, the node for storing the message reach task is deployed in the flink distributed big data computing engine, so that mysql is called from the database once when the reach limit is not required to be judged every time, and the timeliness of message reach judgment is influenced.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the application, and that for a person skilled in the art, other drawings can be derived from them without inventive effort.

Fig. 1 is a flowchart illustrating a message push management method according to an embodiment of the present application.

Fig. 2 is a schematic structural diagram of a message push management system according to an embodiment of the present application.

Fig. 3 is another schematic structural diagram of a message push management system according to an embodiment of the present application.

Fig. 4 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without inventive step, are within the scope of the present application.

It should be noted that the following is a brief introduction to the background of the present solution:

the technical problem that the timeliness of message reach judgment is influenced by one mysql calling operation from the database when message reach limitation is judged each time is mainly solved around the technical problem that a flink distributed big data computing engine and a database are deployed at different nodes. It is understood that in the field of big data marketing systems, it is common to circle a certain size of crowd through a series of rules and then reach the message for this part of the crowd. Such as short message reach, pop window reach, weChat reach, push reach, or webhook reach. But as a big data marketing system, the user volume level reached each time can reach the level of tens of millions or even hundreds of millions, so that the accurate and quick sending of the big data level message is an important technical point of a push system.

The push system has an important link, namely the limitation is reached, for example, within 10 days, the number of messages pushed to a user is not more than N, and the excessive messages may cause harassment to the user. The limited dimensionality of a single user is multiple, for example, the limited dimensionality is more and more, the type level of a touch channel (short message, push, weChat and the like), the level of the touch channel (aurora push, chuanlan push and the like), the level of a touch channel account number (for example, an account number pushed by aurora), the level of a pushing strategy of a marketing canvas and the like are reached. And meanwhile, the limitation of combination types also occurs, such as the touch limitation of combining a plurality of touch channels or the touch limitation of combining a plurality of touch channel account numbers.

In the prior art, a message reach task is generally stored in a database, a calculation layer uses a flink distributed big data calculation engine, and when the message reach task is sent to a single user every time, the message reach task is subjected to data in a fixed time range through the database and then judged through the flink calculation layer. The above scheme has several problems:

3. the database generally has an upper storage limit, but in a big data scene, the message reaching tasks of different dimensionalities of each user need to be recorded, and the database generally does not have distributed expansion capability and has obvious storage and performance bottlenecks;

In order to solve the foregoing technical problem, an embodiment of the present application provides a message push management method. By the message pushing management method, the nodes for storing the message reach tasks are deployed in the flink distributed big data computing engine, so that mysql calling operation is not required to be carried out from the database once when the reach limit is judged every time, and timeliness of message reach judgment is affected.

It should be explained that the Flink distributed big data computation engine is a distributed processing engine for real-time streaming data and batch data. Real-time stream computation refers to processing of data streams, and is a way of real-time computation. Batch computing refers to a data computing mode of uniformly collecting data, storing the data into a database and then processing the data in batches.

Referring to fig. 1, fig. 1 is a schematic flowchart illustrating a message push management method according to an embodiment of the present disclosure. The message push management method is applied to terminal equipment. Optionally, the terminal device is a terminal or a server. Optionally, the server is an independent physical server, or a server cluster or distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as cloud service, cloud database, cloud computing, cloud function, cloud storage, web service, cloud communication, middleware service, domain name service, security service, CDN (Content Delivery Network), big data and artificial intelligence platform. Optionally, the terminal is a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, a smart voice interaction device, a smart home appliance, a vehicle-mounted terminal, and the like, but is not limited thereto.

In one embodiment, the method is used for a flink distributed big data computing engine, and may include the following steps:

step 101, obtaining a batch of messages to be sent, and analyzing and judging the batch of messages to be sent to obtain an analysis and judgment result.

After the terminal device operating the message push management method provided by the scheme acquires a batch of messages to be sent from the cloud regularly or in real time, because different types of messages to be sent are configured with sending modes in advance, for example, within a specified time, the number of messages to be sent to a user is not more than N, and too many messages may cause disturbance to the user. Meanwhile, multiple limited dimensions exist for a single user, such as a touch channel type level (short message, push, weChat, and the like), a touch channel level (aurora push, chuanlan push, and the like), a touch channel account number level (for example, an account number pushed by aurora), a marketing canvas push strategy level, and the like. Therefore, in order to accurately push the messages to be sent to the corresponding users in a given manner, the messages to be sent in batches are analyzed and judged, and corresponding operations are executed according to the analysis and judgment results.

And 102, determining the sending permission of the batch of messages to be sent according to the analysis and judgment result.

If the analysis and judgment result indicates that the message to be sent can only be sent once in a specified day and the message is sent to the same user in the same day, the message is judged to have no sending authority and should be ignored, and harassment to the user is avoided.

Step 103, determining a target message to be sent with a sending authority, and generating a message reaching task of each target message to be sent according to attribute information contained in the target message to be sent.

The attribute information comprises a touch channel type level, a touch channel account number level and a push strategy level.

In this embodiment, the method includes the steps of determining a touch channel type, a touch channel, a trigger channel account and a push policy corresponding to each limiting dimension according to a touch channel type level, a touch channel level, a trigger channel account level and a push policy level; and generating a message touch task which corresponds to each target message to be sent and comprises a touch channel type, a touch channel account and a push strategy.

In real-time, a message reach task is "reach channel type: short messages; access to the channel: aurora push; triggering a channel account: 1111111111000; push strategy: push once every 1 hour interval.

And 104, storing the message touch task of each target message to be sent to the distributed storage of the flink distributed big data computing engine.

In the embodiment, the message reach tasks of the messages to be sent of all targets are stored in the distributed storage of the flink distributed big data computing engine, the original database storage is removed, the message reach tasks are stored by using the distributed storage in the same cluster with the flink distributed big data computing engine, part of the computation layer is increased, and the judgment speed is increased.

In some embodiments, a serialization protocol forward compatibility mode of protobuf can be adopted to serialize the message reach task, so that the data structures of the message reach task are unified; and storing the serialized message reach tasks to distributed storage. When a newly added reach dimension exists, fields can be added in a compatible mode, the previous statistics and judgment are not influenced, code adjustment is basically not needed, and the method has strong expansion capability. When the information of the user reaches the task each time, the information is stored in an increasing mode in sequence, accumulation is good from back to front during traversal, a part of calculation is completed by a flink distributed big data calculation engine, and the overall calculation performance is improved.

It should be noted that the distributed storage used has a horizontal expansion capability, is not limited by a memory, a cpu, and the like, and can expand the storage capability infinitely by increasing a disk or increasing the number of machines.

In some embodiments, the message reach task may also be stored to an external hdfs distributed storage, which ensures that data is not lost by persisting the data to the external hdfs distributed storage.

And 105, guiding the flink distributed big data computing engine to execute and push the target message to be sent in the distributed storage to the corresponding client according to the description content of the message reach task.

The description content can guide the flink distributed big data computing engine to push the target message to be sent in the distributed storage to the corresponding client. By deploying the nodes for storing the message reach tasks in the flink distributed big data computing engine, mysql is called from the database once when the reach limit is not required to be judged every time, and the timeliness of message reach judgment is influenced.

In some embodiments, a message sending state can be further acquired, and corresponding operations are executed according to the message sending state; if the message sending state is successful, generating a sending success event; and if the message sending state is sending failure, generating a sending failure event, and deleting the message reach task corresponding to the sending failure from the distributed storage.

All the above optional technical solutions may be combined arbitrarily to form optional embodiments of the present application, and are not described herein again.

In particular implementation, the present application is not limited by the execution sequence of the described steps, and some steps may be performed in other sequences or simultaneously without conflict.

As can be seen from the above, the message push management method provided in the embodiment of the present application obtains a batch of messages to be sent, and analyzes and judges the batch of messages to be sent to obtain an analysis and judgment result; determining the sending permission of the batch of messages to be sent according to the analysis and judgment result; determining target messages to be sent with sending permission, and generating message touch tasks of the target messages to be sent according to attribute information contained in the target messages to be sent; storing the message touch task of each target message to be sent to the distributed storage of the flink distributed big data computing engine; and guiding the flink distributed big data computing engine to execute and push the target message to be sent in the distributed storage to the corresponding client according to the description content of the message reach task. By utilizing the message push management method provided by the embodiment of the application, the node for storing the message reach task is deployed in the flink distributed big data computing engine, so that mysql is called from the database once when the reach limit is not required to be judged every time, and the timeliness of message reach judgment is influenced.

The embodiment of the application further provides a message pushing management system, and the message pushing management system can be integrated in the terminal device.

Referring to fig. 2, fig. 2 is a schematic structural diagram of a message push management system according to an embodiment of the present disclosure. The message push management system 30 may include:

the acquiring module 31 is configured to acquire a batch of messages to be sent, and analyze and judge the batch of messages to be sent to obtain an analysis and judgment result;

a determining module 32, configured to determine sending permissions of the batch of messages to be sent according to the analysis and determination result;

a generating module 33, configured to determine a target to-be-sent message with a sending right, and generate a message reaching task of each target to-be-sent message according to attribute information included in the target to-be-sent message;

the storage module 34 is configured to store the message reach task of each target message to be sent to the distributed storage of the flink distributed big data computing engine;

and the pushing module 35 is configured to instruct the flink distributed big data computing engine to execute pushing of the target message to be sent in the distributed storage to the corresponding client according to the description content of the message reach task.

In some embodiments, the attribute information includes a trigger channel type level, a trigger channel account level, and a push policy level.

In some embodiments, the generating module 33 is configured to generate the trigger channel type, the trigger channel account, and the push policy according to the limit dimensions of the trigger channel type level, the trigger channel account level, and the push policy level; and generating a message touch task which corresponds to each target message to be sent and comprises a touch channel type, a touch channel account and a push strategy.

In some embodiments, the system further comprises an execution module, configured to acquire a message sending status, and execute a corresponding operation according to the message sending status; if the message sending state is successful, generating a sending success event; and if the message sending state is sending failure, generating a sending failure event, and deleting the message reach task corresponding to the sending failure from the distributed storage.

In some embodiments, the system further comprises an external storage module for storing the message reach task to an external hdfs distributed storage.

In some embodiments, the storage module 34 is configured to perform serialization processing on the message reach task in a forward compatible manner using a serialization protocol of protobuf, so that a data structure of the message reach task is unified; and storing the serialized message reach tasks to the distributed storage.

In specific implementation, the modules may be implemented as independent entities, or may be combined arbitrarily and implemented as one or several entities.

As can be seen from the above, in the message push management system 30 provided in the embodiment of the present application, the obtaining module 31 is configured to obtain a batch of messages to be sent, and analyze and judge the batch of messages to be sent to obtain an analysis and judgment result; the determining module 32 is configured to determine sending permissions of the batch of messages to be sent according to the analysis and judgment result; the generating module 33 is configured to determine a target to-be-sent message with a sending right, and generate a message reaching task of each target to-be-sent message according to attribute information included in the target to-be-sent message; the storage module 34 is configured to store the message reach task of each target message to be sent to the distributed storage of the flink distributed big data computing engine; the pushing module 35 is configured to instruct the flink distributed big data computing engine to push the target message to be sent in the distributed storage to the corresponding client according to the description content of the message reach task.

Referring to fig. 3, fig. 3 is another structural diagram of a message pushing management system according to an embodiment of the present disclosure, in which the message pushing management system 30 includes a memory 120, one or more processors 180, and one or more applications, where the one or more applications are stored in the memory 120 and configured to be executed by the processor 180; the processor 180 may include an acquisition module 31, a determination module 32, a generation module 33, a storage module 34, and a push module 35. For example, the structures and connection relationships of the above components may be as follows:

the memory 120 may be used to store applications and data. The memory 120 stores applications containing executable code. The application programs may constitute various functional modules. The processor 180 executes various functional applications and data processing by running the application programs stored in the memory 120. Further, the memory 120 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 120 may also include a memory controller to provide the processor 180 with access to the memory 120.

The processor 180 is a control center of the device, connects various parts of the entire terminal using various interfaces and lines, performs various functions of the device and processes data by running or executing an application program stored in the memory 120 and calling data stored in the memory 120, thereby monitoring the entire device. Optionally, processor 180 may include one or more processing cores; preferably, the processor 180 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, an application program, and the like.

Specifically, in this embodiment, the processor 180 loads the executable code corresponding to the process of one or more application programs into the memory 120 according to the following instructions, and the processor 180 runs the application programs stored in the memory 120, thereby implementing various functions:

the message sending method comprises the steps of obtaining a command, wherein the command is used for obtaining batch messages to be sent, and analyzing and judging the batch messages to be sent to obtain an analysis and judgment result;

a determining instruction, configured to determine sending permissions of the batch of messages to be sent according to the analysis and determination result;

generating an instruction, which is used for determining a target message to be sent with sending permission and generating a message touch task of each target message to be sent according to attribute information contained in the target message to be sent;

a storage instruction, configured to store a message reach task of each target message to be sent to the distributed storage of the flink distributed big data computing engine;

and the push instruction is used for guiding the flink distributed big data computing engine to push the target message to be sent in the distributed storage to the corresponding client according to the description content of the message touch task.

In some embodiments, the generating instruction is configured to generate a trigger channel type, a trigger channel account, and a push policy according to the trigger channel type level, the trigger channel account level, and the push policy level, which correspond to each limiting dimension; and generating a message reach task which corresponds to each target message to be sent and comprises a reach channel type, a reach channel account number and a push strategy.

In some embodiments, the program further includes an execution instruction for acquiring a message sending status, and executing a corresponding operation according to the message sending status; if the message sending state is successful, generating a successful sending event; and if the message sending state is sending failure, generating a sending failure event, and deleting the message reach task corresponding to the sending failure from the distributed storage.

In some embodiments, the program further includes external store instructions to store the message reach task to an external hdfs distributed store.

In some embodiments, the storage instruction is configured to perform serialization processing on the message reach task in a forward compatible manner using a serialization protocol of protobuf, so that a data structure of the message reach task is unified; and storing the message reach task after the serialization processing to the distributed storage.

The embodiment of the application also provides the terminal equipment. The terminal device can be a server, a smart phone, a computer, a tablet computer and the like.

Referring to fig. 4, fig. 4 is a schematic structural diagram of a terminal device according to an embodiment of the present application, where the terminal device may be used to implement the message push management method provided in the foregoing embodiment. The terminal device 1200 may be a smart phone or a tablet computer.

As shown in fig. 4, the terminal device 1200 may include an RF (Radio Frequency) circuit 110, a memory 120 including one or more computer-readable storage media (only one shown in the figure), an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a transmission module 170, a processor 180 including one or more processing cores (only one shown in the figure), and a power supply 190. Those skilled in the art will appreciate that the terminal device 1200 configuration shown in fig. 4 is not limiting of the terminal device 1200 and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. Wherein:

the RF circuit 110 is used for receiving and transmitting electromagnetic waves, and performs interconversion between the electromagnetic waves and electrical signals, so as to communicate with a communication network or other devices. The RF circuitry 110 may include various existing circuit elements for performing these functions, such as an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a Subscriber Identity Module (SIM) card, memory, and so forth. The RF circuitry 110 may communicate with various networks such as the internet, an intranet, a wireless network, or with other devices over a wireless network.

The memory 120 may be configured to store a software program and a module, such as a program instruction/module corresponding to the message push management method in the foregoing embodiment, and the processor 180 executes various functional applications and data processing by operating the software program and the module stored in the memory 120, and may automatically select a vibration alert mode to update data according to a current scene where the terminal device is located, so as to ensure that scenes such as a conference and the like are not disturbed, ensure that a user can sense an incoming call, and improve intelligence of the terminal device. Memory 120 may include high speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 120 can further include memory located remotely from the processor 180, which can be connected to the terminal device 1200 through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The input unit 130 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control. In particular, the input unit 130 may include a touch-sensitive surface 131 as well as other input devices 132. Touch-sensitive surface 131, also referred to as a touch-sensitive display screen or touch pad, may collect touch operations by a user on or near it (e.g., operations by a user on touch-sensitive surface 131 or near touch-sensitive surface 131 using a finger, a stylus, or any other suitable object or attachment), and actuate the corresponding connection device according to a predetermined program. Alternatively, the touch-sensitive surface 131 may comprise two parts, a touch detection device and a touch controller. The touch detection device detects a touch orientation of a user, detects a signal brought by touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 180, and can receive and execute commands sent by the processor 180. Additionally, the touch sensitive surface 131 may be implemented using various types of resistive, capacitive, infrared, and surface acoustic waves. In addition to touch-sensitive surface 131, input unit 130 may include other input devices 132. In particular, other input devices 132 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 140 may be used to display information input by a user or information provided to the user and various graphic user interfaces of the terminal apparatus 1200, which may be configured by graphics, text, icons, video, and any combination thereof. The Display unit 140 may include a Display panel 141, and optionally, the Display panel 141 may be configured in the form of an LCD (Liquid Crystal Display), an OLED (Organic Light-Emitting Diode), or the like. Further, touch sensitive surface 131 may overlay display panel 141, and when touch sensitive surface 131 detects a touch operation on or near touch sensitive surface 131, it may be transmitted to processor 180 to determine the type of touch event, and then processor 180 may provide a corresponding visual output on display panel 141 according to the type of touch event. Although in FIG. 4, touch-sensitive surface 131 and display panel 141 are shown as two separate components to implement input and output functions, in some embodiments, touch-sensitive surface 131 may be integrated with display panel 141 to implement input and output functions.

The terminal device 1200 may also include at least one sensor 150, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor that may adjust the brightness of the display panel 141 according to the brightness of ambient light, and a proximity sensor that may turn off the display panel 141 and/or the backlight when the terminal apparatus 1200 is moved to the ear. As one of the motion sensors, the gravity acceleration sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when the mobile phone is stationary, and can be used for applications of recognizing the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which may be further configured in the terminal device 1200, further description is omitted here.

The audio circuitry 160, speaker 161, microphone 162 may provide an audio interface between the user and the terminal device 1200. The audio circuit 160 may transmit the electrical signal converted from the received audio data to the speaker 161, and convert the electrical signal into a sound signal for output by the speaker 161; on the other hand, the microphone 162 converts the collected sound signal into an electric signal, converts the electric signal into audio data after being received by the audio circuit 160, and then outputs the audio data to the processor 180 for processing, and then to the RF circuit 110 to be transmitted to, for example, another terminal, or outputs the audio data to the memory 120 for further processing. The audio circuitry 160 may also include an earbud jack to provide communication of peripheral headphones with the terminal device 1200.

The terminal device 1200, through the transmission module 170 (e.g., wi-Fi module), may assist the user in e-mail, web browsing, streaming media access, etc., which provides the user with wireless broadband internet access. Although fig. 4 shows the transmission module 170, it is understood that it does not belong to the essential constitution of the terminal device 1200, and may be omitted entirely as needed within the scope not changing the essence of the invention.

The processor 180 is a control center of the terminal device 1200, connects various parts of the entire mobile phone by using various interfaces and lines, and performs various functions of the terminal device 1200 and processes data by running or executing software programs and/or modules stored in the memory 120 and calling data stored in the memory 120, thereby performing overall monitoring of the mobile phone. Optionally, processor 180 may include one or more processing cores; in some embodiments, the processor 180 may integrate an application processor, which primarily handles operating systems, user interfaces, applications, etc., and a modem processor, which primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 180.

Terminal device 1200 also includes a power supply 190 for providing power to various components, which in some embodiments may be logically coupled to processor 180 via a power management system, such that functions such as managing power discharge and power consumption may be performed via the power management system. The power supply 190 may also include any component including one or more of a dc or ac power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.

Although not shown, the terminal device 1200 may further include a camera (e.g., a front camera, a rear camera), a bluetooth module, and the like, which are not described in detail herein. Specifically, in this embodiment, the display unit 140 of the terminal device 1200 is a touch screen display, and the terminal device 1200 further includes a memory 120 and one or more programs, wherein the one or more programs are stored in the memory 120 and configured to be executed by the one or more processors 180, and the one or more programs include instructions for:

the system comprises an acquisition instruction, a sending instruction and a sending instruction, wherein the acquisition instruction is used for acquiring a batch of messages to be sent, and analyzing and judging the batch of messages to be sent to obtain an analysis and judgment result;

In some embodiments, the instruction is generated to generate the access channel type, the access channel, the trigger channel account, and the push policy, which correspond to each restricted dimension according to the access channel type level, the access channel level, the trigger channel account level, and the push policy level; and generating a message reach task which corresponds to each target message to be sent and comprises a reach channel type, a reach channel account number and a push strategy.

In some embodiments, the program further includes an execution instruction for acquiring a message sending status, and executing a corresponding operation according to the message sending status; if the message sending state is successful, generating a sending success event; and if the message sending state is sending failure, generating a sending failure event, and deleting the message reach task corresponding to the sending failure from the distributed storage.

The embodiment of the application also provides the terminal equipment. The terminal equipment can be equipment such as a smart phone and a computer.

As can be seen from the above, an embodiment of the present application provides a terminal device 1200, where the terminal device 1200 executes the following steps:

An embodiment of the present application further provides a storage medium, where a computer program is stored in the storage medium, and when the computer program runs on a computer, the computer executes the message push management method according to any one of the foregoing embodiments.

It should be noted that, for the message push management method described in the present application, it can be understood by a person skilled in the art that all or part of the process of implementing the message push management method described in the embodiment of the present application may be implemented by controlling related hardware through a computer program, where the computer program may be stored in a computer readable storage medium, such as a memory of a terminal device, and executed by at least one processor in the terminal device, and during the execution process, the process of the embodiment of the message push management method may be included. The storage medium may be a magnetic disk, an optical disk, a Read Only Memory (ROM), a Random Access Memory (RAM), or the like.

For the message push management system in the embodiment of the present application, each functional module may be integrated in one processing chip, or each module may exist alone physically, or two or more modules are integrated in one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium, such as a read-only memory, a magnetic or optical disk, or the like.

The message push management method, device, medium, and apparatus provided in the embodiments of the present application are described in detail above. The principle and the embodiment of the present application are explained by applying specific examples, and the above description of the embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A message pushing management method is used for a flink distributed big data computing engine and is characterized by comprising the following steps:

2. The message push management method according to claim 1, characterized in that the attribute information comprises a reach channel type level, a reach channel account level, a push policy level.

3. The message push management method according to claim 2, wherein the generating of the message reach task for each target message to be sent according to the attribute information included in the target message to be sent comprises:

according to the touch channel type level, the touch channel level, the trigger channel account number level and the push strategy level, the touch channel type, the touch channel, the trigger channel account number and the push strategy corresponding to each limiting dimension;

4. The message push management method according to claim 1, wherein after the pushing of the target message to be sent to the push address corresponding to the target message to be sent is performed according to the determined message sending manner, the method further comprises:

if the message sending state is successful, generating a successful sending event;

5. The message push management method of claim 1, wherein the method further comprises:

and storing the message reach task to an external hdfs distributed storage.

6. The message push management method according to claim 1, wherein the storing the message reach task of each target message to be sent to the distributed storage of the flink distributed big data computing engine comprises:

serializing the message touch task by adopting a forward compatible mode of a serialization protocol of protobuf, so that the data structure of the message touch task is unified;

7. A message pushing management system for a flink distributed big data computing engine, the message pushing management system comprising:

the acquisition module is used for acquiring a batch of messages to be sent, analyzing and judging the batch of messages to be sent and obtaining an analysis and judgment result;

the determining module is used for determining the sending permission of the batch of messages to be sent according to the analysis and judgment result;

the generating module is used for determining target messages to be sent with sending permission and generating message touch tasks of the target messages to be sent according to attribute information contained in the target messages to be sent;

the storage module is used for storing the message touch task of each target message to be sent to the distributed storage of the flink distributed big data computing engine;

and the pushing module is used for guiding the flink distributed big data computing engine to execute and push the target message to be sent in the distributed storage to the corresponding client according to the description content of the message reach task.

8. The message push management system as in claim 7, wherein the attribute information comprises a reach channel type level, a reach channel account level, a push policy level.

9. A computer-readable storage medium storing instructions adapted to be loaded by a processor to perform the message push management method according to any one of claims 1 to 6.

10. A terminal device, comprising a processor and a memory, wherein the memory stores a plurality of instructions, and the processor loads the instructions to execute the message push management method according to any one of claims 1 to 6.